Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb39a8b4fb16c9bb368d1fae07a894e4f5aa428ca69dd58af7f9f8200a381a77

Tx prefix hash: 646fb6940f70b9117127cc21b786301d8cad365acb0d987ae1de1d732b74cb74
Tx public key: fc9cccac1814a2b3f3190f218ee296a4851968a65cb3514f7642137d40855cdd
Timestamp: 1617064314 Timestamp [UCT]: 2021-03-30 00:31:54 Age [y:d:h:m:s]: 04:194:00:38:18
Block: 229339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156495 RingCT/type: yes/0
Extra: 01fc9cccac1814a2b3f3190f218ee296a4851968a65cb3514f7642137d40855cdd02110000003e0dc70aa7000000000000000000

1 output(s) for total of 106.685469409000 dcy

stealth address amount amount idx
00: dc84fde49c96ccad6ce14d4793642f57842ae564fe6382413d27500eac4e5a8a 106.685469409000 475829 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": 229349, "vin": [ { "gen": { "height": 229339 } } ], "vout": [ { "amount": 106685469409, "target": { "key": "dc84fde49c96ccad6ce14d4793642f57842ae564fe6382413d27500eac4e5a8a" } } ], "extra": [ 1, 252, 156, 204, 172, 24, 20, 162, 179, 243, 25, 15, 33, 142, 226, 150, 164, 133, 25, 104, 166, 92, 179, 81, 79, 118, 66, 19, 125, 64, 133, 92, 221, 2, 17, 0, 0, 0, 62, 13, 199, 10, 167, 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