Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a00d7101d91a61b9cfce00bcef3d84fc46b982886246dbd0675d6642667ad5e7

Tx prefix hash: 3d2f73b52f1f8f869c7be7882b7ff167ce4fddb4426f4ee9643ee8e4963407f4
Tx public key: 6e2cf857f541ec86d7caf03f27bc75dc1bf1f6e1a7d325f71df5377eb37e03a4
Timestamp: 1679793332 Timestamp [UCT]: 2023-03-26 01:15:32 Age [y:d:h:m:s]: 01:338:14:35:18
Block: 725125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502626 RingCT/type: yes/0
Extra: 016e2cf857f541ec86d7caf03f27bc75dc1bf1f6e1a7d325f71df5377eb37e03a40211000000015029cbac000000000000000000

1 output(s) for total of 2.428620954000 dcy

stealth address amount amount idx
00: e3dbcc3772acdf307955667b5039dccda32e5a08a0f806aafd22a33ebf46e7b5 2.428620954000 1170208 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": 725135, "vin": [ { "gen": { "height": 725125 } } ], "vout": [ { "amount": 2428620954, "target": { "key": "e3dbcc3772acdf307955667b5039dccda32e5a08a0f806aafd22a33ebf46e7b5" } } ], "extra": [ 1, 110, 44, 248, 87, 245, 65, 236, 134, 215, 202, 240, 63, 39, 188, 117, 220, 27, 241, 246, 225, 167, 211, 37, 247, 29, 245, 55, 126, 179, 126, 3, 164, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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