Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979865673ab10cdce592bff5f88b8f0f1afee588c503edfa544a19680d01b846

Tx prefix hash: e69616dd34381bc79614d332e22544b73c2a26631d60c036850ae313a0897fc2
Tx public key: f42b98b1cf64b03c4b90e302fef4c64983a58b2d3a4465604c716419ca1b6f44
Timestamp: 1736794768 Timestamp [UCT]: 2025-01-13 18:59:28 Age [y:d:h:m:s]: 00:305:05:57:15
Block: 1196651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215666 RingCT/type: yes/0
Extra: 01f42b98b1cf64b03c4b90e302fef4c64983a58b2d3a4465604c716419ca1b6f440211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e10d0dc7897fe3188f9d9ebe1a2eede8806ac8a16a31ce9cd92993a0eac6c5a 0.600000000000 1683252 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": 1196661, "vin": [ { "gen": { "height": 1196651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e10d0dc7897fe3188f9d9ebe1a2eede8806ac8a16a31ce9cd92993a0eac6c5a" } } ], "extra": [ 1, 244, 43, 152, 177, 207, 100, 176, 60, 75, 144, 227, 2, 254, 244, 198, 73, 131, 165, 139, 45, 58, 68, 101, 96, 76, 113, 100, 25, 202, 27, 111, 68, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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