Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09dd0faaefbf2217512967915320b5cb44bf2560317a0d4528dcd315d63c8148

Tx prefix hash: 8010a5f8c7a2d5e2002708feba3a1f0c638808380a878767e150fe99878dc24e
Tx public key: 1184f027f2d1336868eff7c9fe24a19fe952f6a2f041575a0f4e892b3c245ceb
Timestamp: 1713936021 Timestamp [UCT]: 2024-04-24 05:20:21 Age [y:d:h:m:s]: 00:205:05:28:15
Block: 1007281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146916 RingCT/type: yes/0
Extra: 011184f027f2d1336868eff7c9fe24a19fe952f6a2f041575a0f4e892b3c245ceb02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0169b482e43064072ff931ecd5f6c5c1c5939a82d4c406068bdbffcfbb4d755a 0.600000000000 1468569 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": 1007291, "vin": [ { "gen": { "height": 1007281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0169b482e43064072ff931ecd5f6c5c1c5939a82d4c406068bdbffcfbb4d755a" } } ], "extra": [ 1, 17, 132, 240, 39, 242, 209, 51, 104, 104, 239, 247, 201, 254, 36, 161, 159, 233, 82, 246, 162, 240, 65, 87, 90, 15, 78, 137, 43, 60, 36, 92, 235, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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