Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb719f0654c9f9cb52cb30af0fabf368e7b97f754152a238c04e0cea3409235b

Tx prefix hash: 333da9963dfc010c6f2432a5a6bb6056baf8a7d971822d4ff4a2bd1788676a48
Tx public key: a4b6dc12da03cef2e9515727b210340fc23cf48d4e94e5a3dfc61d3d6f8ea909
Timestamp: 1709299706 Timestamp [UCT]: 2024-03-01 13:28:26 Age [y:d:h:m:s]: 01:047:08:42:13
Block: 968853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294843 RingCT/type: yes/0
Extra: 01a4b6dc12da03cef2e9515727b210340fc23cf48d4e94e5a3dfc61d3d6f8ea9090211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84b7b810b1554855ccc886422376b18767601c332a60b683b382b98030f08c86 0.600000000000 1428676 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": 968863, "vin": [ { "gen": { "height": 968853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84b7b810b1554855ccc886422376b18767601c332a60b683b382b98030f08c86" } } ], "extra": [ 1, 164, 182, 220, 18, 218, 3, 206, 242, 233, 81, 87, 39, 178, 16, 52, 15, 194, 60, 244, 141, 78, 148, 229, 163, 223, 198, 29, 61, 111, 142, 169, 9, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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