Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad3973bee634386416558e9eed5d82d9d9143175b2a15ede8e7dd1223eb1d7d1

Tx prefix hash: cf95b9dd65cbec53ecd6f2a716e047468758669fcb4db291d1e0099eca8d7dc9
Tx public key: f5cfc9780a1a6db5851113a3efb128f4d3f4f2f5503fb153b38ab95988818b42
Timestamp: 1585040502 Timestamp [UCT]: 2020-03-24 09:01:42 Age [y:d:h:m:s]: 04:314:11:55:17
Block: 87801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121516 RingCT/type: yes/0
Extra: 01f5cfc9780a1a6db5851113a3efb128f4d3f4f2f5503fb153b38ab95988818b4202110000029b6fa03929000000000000000000

1 output(s) for total of 314.108448440000 dcy

stealth address amount amount idx
00: e15eef1eb045b4f1467e7411e2c3534e546010a3cbd8215be5ba6c4c6f2b81ce 314.108448440000 158049 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": 87811, "vin": [ { "gen": { "height": 87801 } } ], "vout": [ { "amount": 314108448440, "target": { "key": "e15eef1eb045b4f1467e7411e2c3534e546010a3cbd8215be5ba6c4c6f2b81ce" } } ], "extra": [ 1, 245, 207, 201, 120, 10, 26, 109, 181, 133, 17, 19, 163, 239, 177, 40, 244, 211, 244, 242, 245, 80, 63, 177, 83, 179, 138, 185, 89, 136, 129, 139, 66, 2, 17, 0, 0, 2, 155, 111, 160, 57, 41, 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