Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed51d3b44207b73e380eee22f768d45b710bfbb3ae65d90f4308720249769b66

Tx prefix hash: e68c9131012c0c9fd80955798b0779f76a8c6b0278000da8ca4a0d7a21795e6f
Tx public key: dd2986ab058c816bfd0bdcd9ca9887652eec50f8cb79e29d6d2d21c15c96f481
Timestamp: 1576643493 Timestamp [UCT]: 2019-12-18 04:31:33 Age [y:d:h:m:s]: 05:012:15:59:08
Block: 28248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156994 RingCT/type: yes/0
Extra: 01dd2986ab058c816bfd0bdcd9ca9887652eec50f8cb79e29d6d2d21c15c96f48102110000000aad433a0b000000000000000000

1 output(s) for total of 494.770177617000 dcy

stealth address amount amount idx
00: bca75fa113bacd794ff4cf8cda3bc0f7a7ae26903769e56979fd79cca85960b4 494.770177617000 46778 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": 28258, "vin": [ { "gen": { "height": 28248 } } ], "vout": [ { "amount": 494770177617, "target": { "key": "bca75fa113bacd794ff4cf8cda3bc0f7a7ae26903769e56979fd79cca85960b4" } } ], "extra": [ 1, 221, 41, 134, 171, 5, 140, 129, 107, 253, 11, 220, 217, 202, 152, 135, 101, 46, 236, 80, 248, 203, 121, 226, 157, 109, 45, 33, 193, 92, 150, 244, 129, 2, 17, 0, 0, 0, 10, 173, 67, 58, 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