Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6859e7dca525415d055c6bf0821aa00ba8f51b916810f318fc65657917378dcd

Tx prefix hash: d9d3286bf37d9d8fef4e2b502a26c4a9217b21a178f453a6657ecb8d7cb082ff
Tx public key: 90a50e3be128f2959c7167d71f8841c0b017fa75748ef1cd416d4b3f5e4c9148
Timestamp: 1736787668 Timestamp [UCT]: 2025-01-13 17:01:08 Age [y:d:h:m:s]: 00:155:23:03:05
Block: 1196596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111165 RingCT/type: yes/0
Extra: 0190a50e3be128f2959c7167d71f8841c0b017fa75748ef1cd416d4b3f5e4c91480211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 436d91f8e9233b86e71dafae70b2afa71b3d58108d4622ab308b206be9d66343 0.600000000000 1683195 of 15

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": 1196606, "vin": [ { "gen": { "height": 1196596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "436d91f8e9233b86e71dafae70b2afa71b3d58108d4622ab308b206be9d66343" } } ], "extra": [ 1, 144, 165, 14, 59, 225, 40, 242, 149, 156, 113, 103, 215, 31, 136, 65, 192, 176, 23, 250, 117, 116, 142, 241, 205, 65, 109, 75, 63, 94, 76, 145, 72, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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