Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 607c3668988b1b494e5ee5b9922403b7758bf3ae4aa4e1f60c8433a450c6dc24

Tx prefix hash: da082c9e6b144ac78089f54f9545937cb80657b430e8fb8c2180951536032887
Tx public key: 297be04e6f47d62f9ded8ab273fc460fd6e4d47c56d9fcec4d25d7ab29be10b2
Timestamp: 1729796267 Timestamp [UCT]: 2024-10-24 18:57:47 Age [y:d:h:m:s]: 00:159:01:42:33
Block: 1138730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113482 RingCT/type: yes/0
Extra: 01297be04e6f47d62f9ded8ab273fc460fd6e4d47c56d9fcec4d25d7ab29be10b2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0142def35ba50c2600e70cdb8ca635d584aa6989c824eff429262d88755daae5 0.600000000000 1622441 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": 1138740, "vin": [ { "gen": { "height": 1138730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0142def35ba50c2600e70cdb8ca635d584aa6989c824eff429262d88755daae5" } } ], "extra": [ 1, 41, 123, 224, 78, 111, 71, 214, 47, 157, 237, 138, 178, 115, 252, 70, 15, 214, 228, 212, 124, 86, 217, 252, 236, 77, 37, 215, 171, 41, 190, 16, 178, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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