Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdb24d346acb84407e39ea42ea3981867171a3f61c9e3244b698d01efa3d2da1

Tx prefix hash: 8b300ba20ed15b810ec0254aede005e1d7038d359d17e10241c75f30f28856ce
Tx public key: a9f0b10f0a8e3dcef90645796cf74c54e84d3ded4b9fd8733e33209b41a7e220
Timestamp: 1580720519 Timestamp [UCT]: 2020-02-03 09:01:59 Age [y:d:h:m:s]: 04:338:19:20:39
Block: 57844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133370 RingCT/type: yes/0
Extra: 01a9f0b10f0a8e3dcef90645796cf74c54e84d3ded4b9fd8733e33209b41a7e2200211000000304943cd9f000000000000000000

1 output(s) for total of 394.790685614000 dcy

stealth address amount amount idx
00: 61661eed01e03a15507023810cd43cb59a778b476be820448a617413590a727a 394.790685614000 106936 of 0

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": 57854, "vin": [ { "gen": { "height": 57844 } } ], "vout": [ { "amount": 394790685614, "target": { "key": "61661eed01e03a15507023810cd43cb59a778b476be820448a617413590a727a" } } ], "extra": [ 1, 169, 240, 177, 15, 10, 142, 61, 206, 249, 6, 69, 121, 108, 247, 76, 84, 232, 77, 61, 237, 75, 159, 216, 115, 62, 51, 32, 155, 65, 167, 226, 32, 2, 17, 0, 0, 0, 48, 73, 67, 205, 159, 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