Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09cfd21bf5d4220cbf548231c9fde6787d9049837458c956e61ed00a48e9f0ac

Tx prefix hash: 227f19985db4fe4d165ef0d883b4c3cff262ea9aa9b9dfea4d8d8b7e1d218f06
Tx public key: e367da5d2c9f2d77ff07b6147c7e7c0e97a8d49be50ba9d5c4d5d146b8c111ec
Timestamp: 1733962703 Timestamp [UCT]: 2024-12-12 00:18:23 Age [y:d:h:m:s]: 00:100:14:42:34
Block: 1173221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71684 RingCT/type: yes/0
Extra: 01e367da5d2c9f2d77ff07b6147c7e7c0e97a8d49be50ba9d5c4d5d146b8c111ec021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e31658c931359401d88dbbcdcb6cf6222ed176eec595ca4cfff2c90137119cd 0.600000000000 1659218 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": 1173231, "vin": [ { "gen": { "height": 1173221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e31658c931359401d88dbbcdcb6cf6222ed176eec595ca4cfff2c90137119cd" } } ], "extra": [ 1, 227, 103, 218, 93, 44, 159, 45, 119, 255, 7, 182, 20, 124, 126, 124, 14, 151, 168, 212, 155, 229, 11, 169, 213, 196, 213, 209, 70, 184, 193, 17, 236, 2, 17, 0, 0, 0, 1, 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