Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c631323306815311c42029d5344e5b7f49e89197f8e512e2218f6be90658c7ab

Tx prefix hash: a744982c6a9587bd39aab8a97e6d62bf1ed2e4532f703f3b0aaddc6cf5a32fed
Tx public key: f14ca8fc64b4970db1e29ca18dce78d3c408bb4b60a2bc90f9b4abbfbbc28582
Timestamp: 1709413462 Timestamp [UCT]: 2024-03-02 21:04:22 Age [y:d:h:m:s]: 01:066:01:25:20
Block: 969794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308233 RingCT/type: yes/0
Extra: 01f14ca8fc64b4970db1e29ca18dce78d3c408bb4b60a2bc90f9b4abbfbbc285820211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f32d1a0386430e72b176e8c9ecaba29382987e195428a57c2dae224a946e53ef 0.600000000000 1429639 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": 969804, "vin": [ { "gen": { "height": 969794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f32d1a0386430e72b176e8c9ecaba29382987e195428a57c2dae224a946e53ef" } } ], "extra": [ 1, 241, 76, 168, 252, 100, 180, 151, 13, 177, 226, 156, 161, 141, 206, 120, 211, 196, 8, 187, 75, 96, 162, 188, 144, 249, 180, 171, 191, 187, 194, 133, 130, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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