Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeabdc80312c214c47410a6819a3620c6851b66fae454d7c945fe441c3735812

Tx prefix hash: 451a4d23c14b839e93a85558fc71ee3029a4e16dc98d22d88f4dd7acc3432da6
Tx public key: 9c6d21c13baabbe2d873bca017ec8ca2e8acfb836eb52421755bc4ced31e02de
Timestamp: 1728589766 Timestamp [UCT]: 2024-10-10 19:49:26 Age [y:d:h:m:s]: 00:154:02:44:52
Block: 1128771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109936 RingCT/type: yes/0
Extra: 019c6d21c13baabbe2d873bca017ec8ca2e8acfb836eb52421755bc4ced31e02de021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1e9ea2857c1b32d8a3ae911db6e4a309757bee751044031b99a186a17235811 0.600000000000 1611592 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": 1128781, "vin": [ { "gen": { "height": 1128771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1e9ea2857c1b32d8a3ae911db6e4a309757bee751044031b99a186a17235811" } } ], "extra": [ 1, 156, 109, 33, 193, 59, 170, 187, 226, 216, 115, 188, 160, 23, 236, 140, 162, 232, 172, 251, 131, 110, 181, 36, 33, 117, 91, 196, 206, 211, 30, 2, 222, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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