Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 262574e8d8a824df7642bab483b70f402c9ec478ccef7a68134419f40cb84e7d

Tx prefix hash: d20498f99b8da1fe700d9193f5b16025add01b7e82db415ea34ffeafa8c652a1
Tx public key: 456e968fb4310c0a5d072d0595ac8486ff9f83299d1cf36342a65aa27d304cc4
Timestamp: 1709522739 Timestamp [UCT]: 2024-03-04 03:25:39 Age [y:d:h:m:s]: 01:079:07:38:51
Block: 970702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317726 RingCT/type: yes/0
Extra: 01456e968fb4310c0a5d072d0595ac8486ff9f83299d1cf36342a65aa27d304cc40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1678943dc06a069b3ef006d10873c862de6350c8d56623ed98c70c7924557e3 0.600000000000 1430561 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": 970712, "vin": [ { "gen": { "height": 970702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1678943dc06a069b3ef006d10873c862de6350c8d56623ed98c70c7924557e3" } } ], "extra": [ 1, 69, 110, 150, 143, 180, 49, 12, 10, 93, 7, 45, 5, 149, 172, 132, 134, 255, 159, 131, 41, 157, 28, 243, 99, 66, 166, 90, 162, 125, 48, 76, 196, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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