Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 040647677bd5598044c97212457880c2b51afae533cd1a8773645805465871fa

Tx prefix hash: 5244c835f867387a59c18231f88e880510dba62c57004aa4c9e1e8515a5345e1
Tx public key: b4834df5f784b6622f9a3716fb54a72ac87f4bd27c733f7f83d59a2c7d3fb544
Timestamp: 1696103106 Timestamp [UCT]: 2023-09-30 19:45:06 Age [y:d:h:m:s]: 01:104:22:47:03
Block: 859645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336276 RingCT/type: yes/0
Extra: 01b4834df5f784b6622f9a3716fb54a72ac87f4bd27c733f7f83d59a2c7d3fb54402110000000775e3f0e9000000000000000000

1 output(s) for total of 0.870240522000 dcy

stealth address amount amount idx
00: 04a167b746f55e9755360a9e844d87233a385db485f93034c221fb77703b3fc2 0.870240522000 1313881 of 0

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": 859655, "vin": [ { "gen": { "height": 859645 } } ], "vout": [ { "amount": 870240522, "target": { "key": "04a167b746f55e9755360a9e844d87233a385db485f93034c221fb77703b3fc2" } } ], "extra": [ 1, 180, 131, 77, 245, 247, 132, 182, 98, 47, 154, 55, 22, 251, 84, 167, 42, 200, 127, 75, 210, 124, 115, 63, 127, 131, 213, 154, 44, 125, 63, 181, 68, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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