Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa6f76ae0b3229d92f688da337be620f4cb36ebe67971b38ae7da3ef8ca03e2

Tx prefix hash: 6454ac4347c8e879b5b38d0af9661ff470353c70d001af98b2311717431fb61f
Tx public key: e226144db874de2e3e1fde28e0b19f27b22a540bfe95032be0b57ac162419fe1
Timestamp: 1714405110 Timestamp [UCT]: 2024-04-29 15:38:30 Age [y:d:h:m:s]: 00:303:09:54:19
Block: 1011171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216859 RingCT/type: yes/0
Extra: 01e226144db874de2e3e1fde28e0b19f27b22a540bfe95032be0b57ac162419fe10211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fe1b0f405c1716b15df228d0ad769731310312a9ca940358a0518f3cb67f719 0.600000000000 1473331 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": 1011181, "vin": [ { "gen": { "height": 1011171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fe1b0f405c1716b15df228d0ad769731310312a9ca940358a0518f3cb67f719" } } ], "extra": [ 1, 226, 38, 20, 77, 184, 116, 222, 46, 62, 31, 222, 40, 224, 177, 159, 39, 178, 42, 84, 11, 254, 149, 3, 43, 224, 181, 122, 193, 98, 65, 159, 225, 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