Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6497c60d276d0d87e89c23c7cb9edd09722688e646341715157f7c8ed1ad0646

Tx prefix hash: a5d5dbab45fa296f551d887709f749bce9cc166f4258df0e8ce0a6c41732fa2c
Tx public key: 4b31447eefe573acc7d14fee24a4a43a6159c97b6eb55d241dacbbcc8f77144f
Timestamp: 1706264956 Timestamp [UCT]: 2024-01-26 10:29:16 Age [y:d:h:m:s]: 01:090:21:11:01
Block: 943657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326062 RingCT/type: yes/0
Extra: 014b31447eefe573acc7d14fee24a4a43a6159c97b6eb55d241dacbbcc8f77144f0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b95adf7614a7c37e786747a3e250bba35c0e3c56dc1899aa39dcd8e3e47d2c6 0.600000000000 1401865 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": 943667, "vin": [ { "gen": { "height": 943657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b95adf7614a7c37e786747a3e250bba35c0e3c56dc1899aa39dcd8e3e47d2c6" } } ], "extra": [ 1, 75, 49, 68, 126, 239, 229, 115, 172, 199, 209, 79, 238, 36, 164, 164, 58, 97, 89, 201, 123, 110, 181, 93, 36, 29, 172, 187, 204, 143, 119, 20, 79, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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