Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 712a78b4d726b16d65a89f8430f2b0cd8741e5bfa3c6c9afb92e9e2a477d6d90

Tx prefix hash: eb5ea4a0578e46db48011602ab159a804e10cd68af4935b18d1bf3804fe4e8f8
Tx public key: 43833c9ccdbade37fad1e34ba8b92100e789bc6df546cae33785aa6b88e1ce25
Timestamp: 1745319360 Timestamp [UCT]: 2025-04-22 10:56:00 Age [y:d:h:m:s]: 00:260:17:58:05
Block: 1266954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184152 RingCT/type: yes/0
Extra: 0143833c9ccdbade37fad1e34ba8b92100e789bc6df546cae33785aa6b88e1ce25021100000008dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfd5261b62a922ec8b9fa7c17761eba7423bd5d28b00277f1baee9db52a6b242 0.600000000000 1754179 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": 1266964, "vin": [ { "gen": { "height": 1266954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfd5261b62a922ec8b9fa7c17761eba7423bd5d28b00277f1baee9db52a6b242" } } ], "extra": [ 1, 67, 131, 60, 156, 205, 186, 222, 55, 250, 209, 227, 75, 168, 185, 33, 0, 231, 137, 188, 109, 245, 70, 202, 227, 55, 133, 170, 107, 136, 225, 206, 37, 2, 17, 0, 0, 0, 8, 219, 181, 113, 193, 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