Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 210236f8191898c3cade318dc722443a2366b2749f5f0e9a18a09f338ea11129

Tx prefix hash: 4c7ef80c7aa991b519502117ef12431d59f6609f427f8d6d89c29adf032e9d2e
Tx public key: 2cf0d9a2e6c1413e1bfdba44c4b2733b70684d5028e62ce9746750b33eedc8e0
Timestamp: 1734293065 Timestamp [UCT]: 2024-12-15 20:04:25 Age [y:d:h:m:s]: 00:182:09:39:23
Block: 1175965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130068 RingCT/type: yes/0
Extra: 012cf0d9a2e6c1413e1bfdba44c4b2733b70684d5028e62ce9746750b33eedc8e00211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 025b29fdf04ba0732cb86a4aba8ae7f60349deffccf5ed8208499e30fa216e13 0.600000000000 1662292 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": 1175975, "vin": [ { "gen": { "height": 1175965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "025b29fdf04ba0732cb86a4aba8ae7f60349deffccf5ed8208499e30fa216e13" } } ], "extra": [ 1, 44, 240, 217, 162, 230, 193, 65, 62, 27, 253, 186, 68, 196, 178, 115, 59, 112, 104, 77, 80, 40, 230, 44, 233, 116, 103, 80, 179, 62, 237, 200, 224, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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