Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d15e12c3f4c551abfe93475e231132116a0248bece891cf4365ef11746b73af0

Tx prefix hash: a59dc813ce9a64c06ab2d784807826bd71201b624809d7d0eec7b806c4501868
Tx public key: e9c2e0aa50b25278ccc69457cb385d4c8a68c3100fa86b968490267e52f720f8
Timestamp: 1705942328 Timestamp [UCT]: 2024-01-22 16:52:08 Age [y:d:h:m:s]: 01:145:12:49:57
Block: 940973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365060 RingCT/type: yes/0
Extra: 01e9c2e0aa50b25278ccc69457cb385d4c8a68c3100fa86b968490267e52f720f80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8782b5959171addc76e6473a3876c1aa037428c936df27296ec4a4f62b6ca2a3 0.600000000000 1399115 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": 940983, "vin": [ { "gen": { "height": 940973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8782b5959171addc76e6473a3876c1aa037428c936df27296ec4a4f62b6ca2a3" } } ], "extra": [ 1, 233, 194, 224, 170, 80, 178, 82, 120, 204, 198, 148, 87, 203, 56, 93, 76, 138, 104, 195, 16, 15, 168, 107, 150, 132, 144, 38, 126, 82, 247, 32, 248, 2, 17, 0, 0, 0, 5, 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