Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 584dfe58eac987c9495cacd247d461372d9c78ee228b93de7be19a1a561fd961

Tx prefix hash: 83331d95aec40d9dadc704cf287229fbe8543051d57dce57f45f51eef01e90e4
Tx public key: ee57fa9e62c299e65d03e71cc51d0d376b0ea0de9af519a9cef817db30db5cce
Timestamp: 1705516992 Timestamp [UCT]: 2024-01-17 18:43:12 Age [y:d:h:m:s]: 01:100:05:07:45
Block: 937458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332740 RingCT/type: yes/0
Extra: 01ee57fa9e62c299e65d03e71cc51d0d376b0ea0de9af519a9cef817db30db5cce0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db805d30a9d963a00d298486a0db06b7abefcf5d39f0fecd4044fcf1e6ed573c 0.600000000000 1395512 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": 937468, "vin": [ { "gen": { "height": 937458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db805d30a9d963a00d298486a0db06b7abefcf5d39f0fecd4044fcf1e6ed573c" } } ], "extra": [ 1, 238, 87, 250, 158, 98, 194, 153, 230, 93, 3, 231, 28, 197, 29, 13, 55, 107, 14, 160, 222, 154, 245, 25, 169, 206, 248, 23, 219, 48, 219, 92, 206, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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