Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 988aeeb65a03e87b4cf38daed6848d286ef4393db7052e16f754f1e111e8b946

Tx prefix hash: 7604f075f1c51e70eacf24c8ab323f56b5f354c81b9ca9689077d76374485564
Tx public key: a5d76889b0aba7de3af6b657b1c0d50850bce65f8252c7b48caf6ca1e4698847
Timestamp: 1722035507 Timestamp [UCT]: 2024-07-26 23:11:47 Age [y:d:h:m:s]: 00:302:19:59:17
Block: 1074428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216388 RingCT/type: yes/0
Extra: 01a5d76889b0aba7de3af6b657b1c0d50850bce65f8252c7b48caf6ca1e469884702110000001f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8584a02d4e7a4702fa9b2da70ba19d18e2523a181b044794538f28abd5b1b1b 0.600000000000 1546941 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": 1074438, "vin": [ { "gen": { "height": 1074428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8584a02d4e7a4702fa9b2da70ba19d18e2523a181b044794538f28abd5b1b1b" } } ], "extra": [ 1, 165, 215, 104, 137, 176, 171, 167, 222, 58, 246, 182, 87, 177, 192, 213, 8, 80, 188, 230, 95, 130, 82, 199, 180, 140, 175, 108, 161, 228, 105, 136, 71, 2, 17, 0, 0, 0, 31, 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