Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d23e82328b06962764f4badd1d922a42949553729c7a43651694aebedbcc48bd

Tx prefix hash: 6878fab03a2ca35ad733f861c7e4728244a82a6b7d2865809fe8c47a20d3a7e6
Tx public key: 654749e3d1ddfd1efbd2969eb4ab280964cdecad8b9a3ba8c779d706533d6344
Timestamp: 1625445196 Timestamp [UCT]: 2021-07-05 00:33:16 Age [y:d:h:m:s]: 03:253:22:47:53
Block: 288374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 951070 RingCT/type: yes/0
Extra: 01654749e3d1ddfd1efbd2969eb4ab280964cdecad8b9a3ba8c779d706533d6344021100000008d142c209000000000000000000

1 output(s) for total of 67.998249960000 dcy

stealth address amount amount idx
00: 21f38cb04492dc883ff8b82ec43c02be311f27221d7a37c446d06bfddf4f6e19 67.998249960000 604201 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 288384, "vin": [ { "gen": { "height": 288374 } } ], "vout": [ { "amount": 67998249960, "target": { "key": "21f38cb04492dc883ff8b82ec43c02be311f27221d7a37c446d06bfddf4f6e19" } } ], "extra": [ 1, 101, 71, 73, 227, 209, 221, 253, 30, 251, 210, 150, 158, 180, 171, 40, 9, 100, 205, 236, 173, 139, 154, 59, 168, 199, 121, 215, 6, 83, 61, 99, 68, 2, 17, 0, 0, 0, 8, 209, 66, 194, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8