Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daaf4e7acd4a607946dbf07a7511a8e8108148d4e7a4ff805839f37f5841e7b7

Tx prefix hash: ed0744e841b9d16ba679ef7fa05a284d3cd90d542fe80c09ef8d1ad6b2f2f0cd
Tx public key: 624d439d3d2bae160a89e3524b191be1109a76980128506c0c2e2a6571b63a29
Timestamp: 1713295511 Timestamp [UCT]: 2024-04-16 19:25:11 Age [y:d:h:m:s]: 00:268:03:41:14
Block: 1001957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191958 RingCT/type: yes/0
Extra: 01624d439d3d2bae160a89e3524b191be1109a76980128506c0c2e2a6571b63a290211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ccd9b59c3bdf439bc9ec36fa37fb1cfb7baadbbdcfcb8254d2161b7b848727c 0.600000000000 1462471 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": 1001967, "vin": [ { "gen": { "height": 1001957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ccd9b59c3bdf439bc9ec36fa37fb1cfb7baadbbdcfcb8254d2161b7b848727c" } } ], "extra": [ 1, 98, 77, 67, 157, 61, 43, 174, 22, 10, 137, 227, 82, 75, 25, 27, 225, 16, 154, 118, 152, 1, 40, 80, 108, 12, 46, 42, 101, 113, 182, 58, 41, 2, 17, 0, 0, 0, 2, 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