Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6499c61ea4ed73ead29bfe8d81dbade060cc7d40f710ce885b4986d14eff145a

Tx prefix hash: 63d011fc4dadd18be259b1a41a4bed87f597e221e80cf669c822a2047169adbf
Tx public key: 6cd8803fccdb3c1b2d405cbb69ba8b4776742fae47568f649e9c63cccd7cfab8
Timestamp: 1581945661 Timestamp [UCT]: 2020-02-17 13:21:01 Age [y:d:h:m:s]: 05:261:16:54:41
Block: 66627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1337976 RingCT/type: yes/0
Extra: 016cd8803fccdb3c1b2d405cbb69ba8b4776742fae47568f649e9c63cccd7cfab80211000000017adf42d3000000000000000000

1 output(s) for total of 369.186153853000 dcy

stealth address amount amount idx
00: 0b928aab591e965c43ad3a52e2d17fde1393c2d5a673afca962f24c3ac4a6a4f 369.186153853000 122764 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": 66637, "vin": [ { "gen": { "height": 66627 } } ], "vout": [ { "amount": 369186153853, "target": { "key": "0b928aab591e965c43ad3a52e2d17fde1393c2d5a673afca962f24c3ac4a6a4f" } } ], "extra": [ 1, 108, 216, 128, 63, 204, 219, 60, 27, 45, 64, 92, 187, 105, 186, 139, 71, 118, 116, 47, 174, 71, 86, 143, 100, 158, 156, 99, 204, 205, 124, 250, 184, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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