Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 265f63c34de3fa38172caf0bb84e991a6e9637e409defeee2c9a98ad57dc19b1

Tx prefix hash: 31c72101287941c87e7dfcbefa4ae8ccec34db00cda75c646eafad8ce3e9cd29
Tx public key: efd2ff94e2fb1977ddae0884fa8481fb813cab958a2075c43ed6c8a8a1700d98
Timestamp: 1716608325 Timestamp [UCT]: 2024-05-25 03:38:45 Age [y:d:h:m:s]: 00:232:06:19:32
Block: 1029444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166221 RingCT/type: yes/0
Extra: 01efd2ff94e2fb1977ddae0884fa8481fb813cab958a2075c43ed6c8a8a1700d980211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2eb9859433f4dfe7d0d5b97f4eff9e50e48b7e571b194aff3f2af4b28804947e 0.600000000000 1497535 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": 1029454, "vin": [ { "gen": { "height": 1029444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eb9859433f4dfe7d0d5b97f4eff9e50e48b7e571b194aff3f2af4b28804947e" } } ], "extra": [ 1, 239, 210, 255, 148, 226, 251, 25, 119, 221, 174, 8, 132, 250, 132, 129, 251, 129, 60, 171, 149, 138, 32, 117, 196, 62, 214, 200, 168, 161, 112, 13, 152, 2, 17, 0, 0, 0, 8, 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