Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a383d62890a9d66c876aa1875a30b1b3afbdfd0cca88e7f826d9dc86ccc2803

Tx prefix hash: 6620dd34fa28d992c6db22ca5789b42a630500fc5ac304a8081840135927d581
Tx public key: 08e2f830ac5a11ffe275594a6e9f0acaf2fc3c7f34ae3bdb3abf993a7707bad9
Timestamp: 1720501532 Timestamp [UCT]: 2024-07-09 05:05:32 Age [y:d:h:m:s]: 00:272:17:18:05
Block: 1061721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194829 RingCT/type: yes/0
Extra: 0108e2f830ac5a11ffe275594a6e9f0acaf2fc3c7f34ae3bdb3abf993a7707bad902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f942a86845b5b0852166c990558383be41816a6216d030f3ff0cf1b1347e16aa 0.600000000000 1532216 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": 1061731, "vin": [ { "gen": { "height": 1061721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f942a86845b5b0852166c990558383be41816a6216d030f3ff0cf1b1347e16aa" } } ], "extra": [ 1, 8, 226, 248, 48, 172, 90, 17, 255, 226, 117, 89, 74, 110, 159, 10, 202, 242, 252, 60, 127, 52, 174, 59, 219, 58, 191, 153, 58, 119, 7, 186, 217, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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