Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 432369f7fc8afba3db471e4b5d0517697e6f31b6a9258ca27f7056ea83932d94

Tx prefix hash: a25708a949eecce7bc91367524d942fe07d132e58d7e2baa3881130bdb92263f
Tx public key: f350c40d5c757f4833ed15307f0d461cb9ec6dd48ed81876d310ae5aea648f03
Timestamp: 1712236645 Timestamp [UCT]: 2024-04-04 13:17:25 Age [y:d:h:m:s]: 01:242:15:16:04
Block: 993164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432150 RingCT/type: yes/0
Extra: 01f350c40d5c757f4833ed15307f0d461cb9ec6dd48ed81876d310ae5aea648f0302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f591b7ee5a0992fa15d4e0af62d7b5c9233d50c5cd33f2fba003cb5d038a24 0.600000000000 1453546 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": 993174, "vin": [ { "gen": { "height": 993164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f591b7ee5a0992fa15d4e0af62d7b5c9233d50c5cd33f2fba003cb5d038a24" } } ], "extra": [ 1, 243, 80, 196, 13, 92, 117, 127, 72, 51, 237, 21, 48, 127, 13, 70, 28, 185, 236, 109, 212, 142, 216, 24, 118, 211, 16, 174, 90, 234, 100, 143, 3, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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