Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2700ecf137de5d1f1fa4ec81953ed9ec306d7651c095f9f40385ec0d82aaa8cd

Tx prefix hash: 47849af3e32e37d19d892a5fe229e6df6bb4a103dc5143f5e962f214525cc6eb
Tx public key: 6a66e4c779bb22827a3d62bc9b54f25d33e33a3cf2d447ac4eec654a424951dd
Timestamp: 1731945320 Timestamp [UCT]: 2024-11-18 15:55:20 Age [y:d:h:m:s]: 00:171:09:50:37
Block: 1156488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122344 RingCT/type: yes/0
Extra: 016a66e4c779bb22827a3d62bc9b54f25d33e33a3cf2d447ac4eec654a424951dd0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de7f2311b48b12200b75e9b8c65c22a4eb215c402790632cebc07be10612e192 0.600000000000 1642111 of 15

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": 1156498, "vin": [ { "gen": { "height": 1156488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de7f2311b48b12200b75e9b8c65c22a4eb215c402790632cebc07be10612e192" } } ], "extra": [ 1, 106, 102, 228, 199, 121, 187, 34, 130, 122, 61, 98, 188, 155, 84, 242, 93, 51, 227, 58, 60, 242, 212, 71, 172, 78, 236, 101, 74, 66, 73, 81, 221, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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