Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba9dfd1f3c4172f5e28764e6677f9d06b4bd4de2b6ac7144f2723d09df4eda9

Tx prefix hash: d22a7ea3dba994072e4fc0c102ea1888a0852824417b986dc91fe2e7e111fbfa
Tx public key: 4f070addad99c0dce2d52ac5dd506f01bb777030f626210de8107e111e86dc01
Timestamp: 1710566626 Timestamp [UCT]: 2024-03-16 05:23:46 Age [y:d:h:m:s]: 01:029:12:05:37
Block: 979368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282060 RingCT/type: yes/0
Extra: 014f070addad99c0dce2d52ac5dd506f01bb777030f626210de8107e111e86dc0102110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a9fc93307c5c58b3f916e3fb567cf8aa9de1968cb501d165bcea65114f0ffc 0.600000000000 1439401 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": 979378, "vin": [ { "gen": { "height": 979368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a9fc93307c5c58b3f916e3fb567cf8aa9de1968cb501d165bcea65114f0ffc" } } ], "extra": [ 1, 79, 7, 10, 221, 173, 153, 192, 220, 226, 213, 42, 197, 221, 80, 111, 1, 187, 119, 112, 48, 246, 38, 33, 13, 232, 16, 126, 17, 30, 134, 220, 1, 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