Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23d314f853b909ce03dfcb326d9b8a684b2be634936bc0cbad40f38a33119b6d

Tx prefix hash: 0a581d1de35ce06f237a265a89756c709e2d44b8470a3962628f8b10a5b389ae
Tx public key: 56775c0da6a2b82515e8988c4c7f827299bd2b3340906b75457d40f49821810c
Timestamp: 1715100608 Timestamp [UCT]: 2024-05-07 16:50:08 Age [y:d:h:m:s]: 01:009:21:17:18
Block: 1016939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267994 RingCT/type: yes/0
Extra: 0156775c0da6a2b82515e8988c4c7f827299bd2b3340906b75457d40f49821810c0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eed8da92963c43da55a4671d9ebfcb20519bfa502ddfebb7e8292b0018a7b6e 0.600000000000 1480672 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": 1016949, "vin": [ { "gen": { "height": 1016939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eed8da92963c43da55a4671d9ebfcb20519bfa502ddfebb7e8292b0018a7b6e" } } ], "extra": [ 1, 86, 119, 92, 13, 166, 162, 184, 37, 21, 232, 152, 140, 76, 127, 130, 114, 153, 189, 43, 51, 64, 144, 107, 117, 69, 125, 64, 244, 152, 33, 129, 12, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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