Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d23b39531491b79730de2740e025fac6754c69e9a172dcb93cd1ab4d156cc69d

Tx prefix hash: bde78f8f53319713f5cda956a812faf9ad57eb09d79d34ec72fed3a5d31c5ff7
Tx public key: f6d8a9392d7c7883d857748f95e3beee74e82d9420405b3001ba356b4a203e02
Timestamp: 1713564670 Timestamp [UCT]: 2024-04-19 22:11:10 Age [y:d:h:m:s]: 00:353:20:18:49
Block: 1004185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252973 RingCT/type: yes/0
Extra: 01f6d8a9392d7c7883d857748f95e3beee74e82d9420405b3001ba356b4a203e020211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96e7e8320fcf193f7e2df7d5588dd4dc2ac8d780dcd24d5bdd2afa4bb7ef481f 0.600000000000 1464753 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": 1004195, "vin": [ { "gen": { "height": 1004185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96e7e8320fcf193f7e2df7d5588dd4dc2ac8d780dcd24d5bdd2afa4bb7ef481f" } } ], "extra": [ 1, 246, 216, 169, 57, 45, 124, 120, 131, 216, 87, 116, 143, 149, 227, 190, 238, 116, 232, 45, 148, 32, 64, 91, 48, 1, 186, 53, 107, 74, 32, 62, 2, 2, 17, 0, 0, 0, 3, 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