Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed478ff32af2796cf4606b30e4e3f19cc62f3964ead5ce8fe588fb2d73bf97b

Tx prefix hash: 826a6a9647823276237556892868e930a34652b758c0787e85851a9da82d27f2
Tx public key: c967fe1d7bf84f0c1fd646f96f873e018ca39af6a9d3a33b1c3267a56f28cee7
Timestamp: 1724028356 Timestamp [UCT]: 2024-08-19 00:45:56 Age [y:d:h:m:s]: 00:226:14:29:38
Block: 1090957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161820 RingCT/type: yes/0
Extra: 01c967fe1d7bf84f0c1fd646f96f873e018ca39af6a9d3a33b1c3267a56f28cee702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ea0869acea48233bd2671e0f1d3f93a6457ba31540e083631a42040749e6c1d 0.600000000000 1565582 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": 1090967, "vin": [ { "gen": { "height": 1090957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ea0869acea48233bd2671e0f1d3f93a6457ba31540e083631a42040749e6c1d" } } ], "extra": [ 1, 201, 103, 254, 29, 123, 248, 79, 12, 31, 214, 70, 249, 111, 135, 62, 1, 140, 163, 154, 246, 169, 211, 163, 59, 28, 50, 103, 165, 111, 40, 206, 231, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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