Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc9673c08e2f83b29d49d8edd9eb15de7cb3ee2d76703c913210e1be8d3f6a0e

Tx prefix hash: bab8e7f9c9d54f0fef6ffc8e3732bc5a8dc996e51159c78d307cde05439a7c49
Tx public key: 2b4633b9c123a6f662ccc56fcd933fa7051414d43cec007d3f83e5d18c49ba18
Timestamp: 1636638636 Timestamp [UCT]: 2021-11-11 13:50:36 Age [y:d:h:m:s]: 03:185:08:41:21
Block: 372136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 910908 RingCT/type: yes/0
Extra: 012b4633b9c123a6f662ccc56fcd933fa7051414d43cec007d3f83e5d18c49ba18021100000001f79c6ccf000000000000000000

1 output(s) for total of 35.888833461000 dcy

stealth address amount amount idx
00: 2701e80a3d088c4aeaae25ec49a007432a6368f5c21c1bdcc17f59f069a78522 35.888833461000 753904 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": 372146, "vin": [ { "gen": { "height": 372136 } } ], "vout": [ { "amount": 35888833461, "target": { "key": "2701e80a3d088c4aeaae25ec49a007432a6368f5c21c1bdcc17f59f069a78522" } } ], "extra": [ 1, 43, 70, 51, 185, 193, 35, 166, 246, 98, 204, 197, 111, 205, 147, 63, 167, 5, 20, 20, 212, 60, 236, 0, 125, 63, 131, 229, 209, 140, 73, 186, 24, 2, 17, 0, 0, 0, 1, 247, 156, 108, 207, 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