Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8f4891a6c652b7d616002bf5afb3aa67abb5c9fea54be23e5823762e92aa672

Tx prefix hash: 49691fcc64d2d4a4f699bbac133cf87cb071bef828e70bd9e89afc67deb16ccb
Tx public key: 9c0171cef49879638193aa9d1a841880655f3f917c4d3c0638dd5a0c2c003e74
Timestamp: 1736380844 Timestamp [UCT]: 2025-01-09 00:00:44 Age [y:d:h:m:s]: 00:090:06:57:09
Block: 1193227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64306 RingCT/type: yes/0
Extra: 019c0171cef49879638193aa9d1a841880655f3f917c4d3c0638dd5a0c2c003e74021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae8477d4a01298203889a65d0a94c3f1bd9b28647661a05769db97101a2432b9 0.600000000000 1679786 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": 1193237, "vin": [ { "gen": { "height": 1193227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae8477d4a01298203889a65d0a94c3f1bd9b28647661a05769db97101a2432b9" } } ], "extra": [ 1, 156, 1, 113, 206, 244, 152, 121, 99, 129, 147, 170, 157, 26, 132, 24, 128, 101, 95, 63, 145, 124, 77, 60, 6, 56, 221, 90, 12, 44, 0, 62, 116, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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