Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aea4700e6184278b38ba33c6c91dfdaad4c50081395b198b41ac6b9638c8690

Tx prefix hash: 45a6d0b487c0a90411c0dece8c5cb9e7086511ddaeae3d94b112f69a6bf1dba3
Tx public key: 4579f661663a2d873d0be1d1f19ff06725e74cbc1b06047ded6044bffcbf2cac
Timestamp: 1749677023 Timestamp [UCT]: 2025-06-11 21:23:43 Age [y:d:h:m:s]: 00:151:22:21:01
Block: 1303006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106291 RingCT/type: yes/0
Extra: 014579f661663a2d873d0be1d1f19ff06725e74cbc1b06047ded6044bffcbf2cac02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ca91bbc55db8d71863fe195e5ae1d64d1cb446364b8d18c699aec604c3bf03e 0.600000000000 1790581 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": 1303016, "vin": [ { "gen": { "height": 1303006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ca91bbc55db8d71863fe195e5ae1d64d1cb446364b8d18c699aec604c3bf03e" } } ], "extra": [ 1, 69, 121, 246, 97, 102, 58, 45, 135, 61, 11, 225, 209, 241, 159, 240, 103, 37, 231, 76, 188, 27, 6, 4, 125, 237, 96, 68, 191, 252, 191, 44, 172, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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