Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a1205826bca514c952012f3670a6120cb14d368658aa53d314c7ea95ad75365

Tx prefix hash: 2341c82f1a129222087221b14b6d5253aa40b1f76570ad43cbdcdfc64f85686f
Tx public key: 4ce14999aef21d970d89b33cbbc508c2c5c72ccf3c14f10ac346328ad04691b5
Timestamp: 1581823590 Timestamp [UCT]: 2020-02-16 03:26:30 Age [y:d:h:m:s]: 04:361:22:29:16
Block: 65927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150694 RingCT/type: yes/0
Extra: 014ce14999aef21d970d89b33cbbc508c2c5c72ccf3c14f10ac346328ad04691b502110000000103d36d11000000000000000000

1 output(s) for total of 371.156688330000 dcy

stealth address amount amount idx
00: 939e37bfad21bc28a4ca5a8ce00925946f3d7f43a0af9475e30cd777b453b7f0 371.156688330000 121554 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": 65937, "vin": [ { "gen": { "height": 65927 } } ], "vout": [ { "amount": 371156688330, "target": { "key": "939e37bfad21bc28a4ca5a8ce00925946f3d7f43a0af9475e30cd777b453b7f0" } } ], "extra": [ 1, 76, 225, 73, 153, 174, 242, 29, 151, 13, 137, 179, 60, 187, 197, 8, 194, 197, 199, 44, 207, 60, 20, 241, 10, 195, 70, 50, 138, 208, 70, 145, 181, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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