Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 371ff0b3d1361e4dfa3321cad0bd29c14f051f5591080128ec88d3a66ab74bc0

Tx prefix hash: bbed06ff29db8cc0751526fb5baf50d57f4fd4e13b07e2c7788df9357007df93
Tx public key: 61eaa751c091b375cdb20c5926fd49bf2d0c79fa89a22d4655e899ecdb95ca9c
Timestamp: 1713216377 Timestamp [UCT]: 2024-04-15 21:26:17 Age [y:d:h:m:s]: 00:358:21:13:34
Block: 1001292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256587 RingCT/type: yes/0
Extra: 0161eaa751c091b375cdb20c5926fd49bf2d0c79fa89a22d4655e899ecdb95ca9c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfc514bdd4869abd2d2266414f8e2b6fb46974de5376d6d50df6dd6a06ee5585 0.600000000000 1461796 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": 1001302, "vin": [ { "gen": { "height": 1001292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc514bdd4869abd2d2266414f8e2b6fb46974de5376d6d50df6dd6a06ee5585" } } ], "extra": [ 1, 97, 234, 167, 81, 192, 145, 179, 117, 205, 178, 12, 89, 38, 253, 73, 191, 45, 12, 121, 250, 137, 162, 45, 70, 85, 232, 153, 236, 219, 149, 202, 156, 2, 17, 0, 0, 0, 2, 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