Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68145fff67445f6e0f4e159a2b421bec4ff6dd5058ae045faae070dceb145a1d

Tx prefix hash: c873b67cbd3380535bf2f206f64a5ca1a429fbf58f66445d6323b69bd1951f70
Tx public key: e877581feca193d1e15fb9eb22ca5141074406c0c75aa440e94523e95f5178a7
Timestamp: 1733028457 Timestamp [UCT]: 2024-12-01 04:47:37 Age [y:d:h:m:s]: 00:104:01:13:22
Block: 1165474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74167 RingCT/type: yes/0
Extra: 01e877581feca193d1e15fb9eb22ca5141074406c0c75aa440e94523e95f5178a70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8359b8f688ab1c1cce905fc8a50504f8f26f05aa45d0366c1cd7258cb98e66b 0.600000000000 1651149 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": 1165484, "vin": [ { "gen": { "height": 1165474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8359b8f688ab1c1cce905fc8a50504f8f26f05aa45d0366c1cd7258cb98e66b" } } ], "extra": [ 1, 232, 119, 88, 31, 236, 161, 147, 209, 225, 95, 185, 235, 34, 202, 81, 65, 7, 68, 6, 192, 199, 90, 164, 64, 233, 69, 35, 233, 95, 81, 120, 167, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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