Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1a21cd1389fc2a5ebde9d5ec0504b79c41769a138fc03a3f0dc48687be9aa4a

Tx prefix hash: e4617984c99fede5235c908d2baa7255c7ae27a7319dfaf7dbac37403a179b7d
Tx public key: 31f2f7dd8dca73ed2dec04d02a14748b180e0ece3760c6926c71766b2818408f
Timestamp: 1574734368 Timestamp [UCT]: 2019-11-26 02:12:48 Age [y:d:h:m:s]: 05:166:09:16:08
Block: 17587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1261540 RingCT/type: yes/0
Extra: 0131f2f7dd8dca73ed2dec04d02a14748b180e0ece3760c6926c71766b2818408f021100000001f95225a5000000000000000000

1 output(s) for total of 536.707259941000 dcy

stealth address amount amount idx
00: 6943e0a98d55ce748815ec4becfc0be25a11fc1a4fb2bce2e2c6ede57548f2ca 536.707259941000 25787 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": 17597, "vin": [ { "gen": { "height": 17587 } } ], "vout": [ { "amount": 536707259941, "target": { "key": "6943e0a98d55ce748815ec4becfc0be25a11fc1a4fb2bce2e2c6ede57548f2ca" } } ], "extra": [ 1, 49, 242, 247, 221, 141, 202, 115, 237, 45, 236, 4, 208, 42, 20, 116, 139, 24, 14, 14, 206, 55, 96, 198, 146, 108, 113, 118, 107, 40, 24, 64, 143, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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