Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d38bdc7b73732b1bc7104911cba64206e618c27873f24ee643e54b966a3cf503

Tx prefix hash: fe911183c7949af7c68de4e335c1fde95a551fc9c0cfe620a9a3ab937284a2db
Tx public key: fe74366aa717da2fce5af72a984cae6d8ba3412d7d78eff16769b7a3875159ea
Timestamp: 1708306450 Timestamp [UCT]: 2024-02-19 01:34:10 Age [y:d:h:m:s]: 01:119:20:10:20
Block: 960608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346601 RingCT/type: yes/0
Extra: 01fe74366aa717da2fce5af72a984cae6d8ba3412d7d78eff16769b7a3875159ea02110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13d4ee1dd1f1c29d3e2f2be2a2ebea17e19709aef3b59548787177525aef6b21 0.600000000000 1420193 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": 960618, "vin": [ { "gen": { "height": 960608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13d4ee1dd1f1c29d3e2f2be2a2ebea17e19709aef3b59548787177525aef6b21" } } ], "extra": [ 1, 254, 116, 54, 106, 167, 23, 218, 47, 206, 90, 247, 42, 152, 76, 174, 109, 139, 163, 65, 45, 125, 120, 239, 241, 103, 105, 183, 163, 135, 81, 89, 234, 2, 17, 0, 0, 0, 15, 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