Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5fe3d82e180e79fe5f10b103ad9a8478b4f54daff4e175078346d850a1057e0

Tx prefix hash: 3d2efb45385551cace4efc2308392a43d9d3275cba0bdf50b70c07d5a05838e5
Tx public key: f6dca10e0c182c9e2b3b7a9c69f892e4dadc2a1dd448513ec8421de1a35d5109
Timestamp: 1714225832 Timestamp [UCT]: 2024-04-27 13:50:32 Age [y:d:h:m:s]: 00:255:02:14:50
Block: 1009678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182594 RingCT/type: yes/0
Extra: 01f6dca10e0c182c9e2b3b7a9c69f892e4dadc2a1dd448513ec8421de1a35d510902110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c13c5ae9277100b4af754f81acd814c25363b9a7c0fcbed9c773a095d5a0729e 0.600000000000 1471418 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": 1009688, "vin": [ { "gen": { "height": 1009678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c13c5ae9277100b4af754f81acd814c25363b9a7c0fcbed9c773a095d5a0729e" } } ], "extra": [ 1, 246, 220, 161, 14, 12, 24, 44, 158, 43, 59, 122, 156, 105, 248, 146, 228, 218, 220, 42, 29, 212, 72, 81, 62, 200, 66, 29, 225, 163, 93, 81, 9, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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