Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 283ae64bfee041b8c2040d5f3fd9931947864afe47c1a8468b14f49fd6da34fb

Tx prefix hash: 9f7f96b0538c0fc8b3dbe6c51ec5fb4ae9814f71cd5b751dfc25085c81d184b5
Tx public key: ed640bcade101fac2622dc3ca4e43b892f9ef8a2953f3174957b10efa6dc6544
Timestamp: 1737467189 Timestamp [UCT]: 2025-01-21 13:46:29 Age [y:d:h:m:s]: 00:151:07:46:20
Block: 1202171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107850 RingCT/type: yes/0
Extra: 01ed640bcade101fac2622dc3ca4e43b892f9ef8a2953f3174957b10efa6dc65440211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcb95989e2ae1129b6009ec718080a2d75dfade62a224ff64b705f24686e570e 0.600000000000 1688834 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": 1202181, "vin": [ { "gen": { "height": 1202171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcb95989e2ae1129b6009ec718080a2d75dfade62a224ff64b705f24686e570e" } } ], "extra": [ 1, 237, 100, 11, 202, 222, 16, 31, 172, 38, 34, 220, 60, 164, 228, 59, 137, 47, 158, 248, 162, 149, 63, 49, 116, 149, 123, 16, 239, 166, 220, 101, 68, 2, 17, 0, 0, 0, 6, 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