Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4978cece8e78609b5ce1f5fbe6ee9aa2627fd0b48f02c1d18acaf8451ee82a

Tx prefix hash: 737ae9334247524dc4e01eb85a38b697ccac3cdd9d9bc0516962e1468a302dfd
Tx public key: 12f6d9faedc8efc55d16db84799010f0f85ca7ffc591520dd38a248e67bbf01a
Timestamp: 1608839172 Timestamp [UCT]: 2020-12-24 19:46:12 Age [y:d:h:m:s]: 04:113:07:15:05
Block: 168665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093766 RingCT/type: yes/0
Extra: 0112f6d9faedc8efc55d16db84799010f0f85ca7ffc591520dd38a248e67bbf01a0211000002c7b9b01d0b000000000000000000

1 output(s) for total of 169.497636332000 dcy

stealth address amount amount idx
00: 03d13be70fd606159bba17d38b518f7dba877fee472b6621afb04451013ff223 169.497636332000 313424 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": 168675, "vin": [ { "gen": { "height": 168665 } } ], "vout": [ { "amount": 169497636332, "target": { "key": "03d13be70fd606159bba17d38b518f7dba877fee472b6621afb04451013ff223" } } ], "extra": [ 1, 18, 246, 217, 250, 237, 200, 239, 197, 93, 22, 219, 132, 121, 144, 16, 240, 248, 92, 167, 255, 197, 145, 82, 13, 211, 138, 36, 142, 103, 187, 240, 26, 2, 17, 0, 0, 2, 199, 185, 176, 29, 11, 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