Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c13a79f06a2f1823cbf8acf0e602af48d3342acc6d314ea24c66471096abf0

Tx prefix hash: ea3008d7e086c74e699255589676bde36e7ed1364755f13731c0ff69673e8320
Tx public key: ac62e6d65a53e4e13ee9f89e07c53fcd1b7d46c72aa565bf21bab7b088131cef
Timestamp: 1734577689 Timestamp [UCT]: 2024-12-19 03:08:09 Age [y:d:h:m:s]: 00:106:21:34:27
Block: 1178327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76162 RingCT/type: yes/0
Extra: 01ac62e6d65a53e4e13ee9f89e07c53fcd1b7d46c72aa565bf21bab7b088131cef021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3648dbe623356eac4c2606f48c2d4dee123cf378aa634e0775869f8123944e8 0.600000000000 1664714 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": 1178337, "vin": [ { "gen": { "height": 1178327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3648dbe623356eac4c2606f48c2d4dee123cf378aa634e0775869f8123944e8" } } ], "extra": [ 1, 172, 98, 230, 214, 90, 83, 228, 225, 62, 233, 248, 158, 7, 197, 63, 205, 27, 125, 70, 199, 42, 165, 101, 191, 33, 186, 183, 176, 136, 19, 28, 239, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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