Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6a2d4d3692163a8572a3ecb348990eed63e78238731e65cdc1a1f53514e9550

Tx prefix hash: 65a9ed76dcb0ea3ff73263ce9a5e4eaefdaa8ece089824d0d6fa2734e4834200
Tx public key: 2d19b1a8b7d0dafc5abde6e20b8bd66a923b1e94b8c839339c97e1d88c4ae991
Timestamp: 1736522913 Timestamp [UCT]: 2025-01-10 15:28:33 Age [y:d:h:m:s]: 00:161:20:34:33
Block: 1194399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115339 RingCT/type: yes/0
Extra: 012d19b1a8b7d0dafc5abde6e20b8bd66a923b1e94b8c839339c97e1d88c4ae9910211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a64e4035b8b30f50f7a09eba8786f74beeb78a50d3bfc08bf91a89ea98162544 0.600000000000 1680970 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": 1194409, "vin": [ { "gen": { "height": 1194399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a64e4035b8b30f50f7a09eba8786f74beeb78a50d3bfc08bf91a89ea98162544" } } ], "extra": [ 1, 45, 25, 177, 168, 183, 208, 218, 252, 90, 189, 230, 226, 11, 139, 214, 106, 146, 59, 30, 148, 184, 200, 57, 51, 156, 151, 225, 216, 140, 74, 233, 145, 2, 17, 0, 0, 0, 7, 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