Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0050a8c8174222a4c4d663e7ae821b43f22f83cc0b5de591ac49f293a7b356c

Tx prefix hash: 6d68fcecd97ed8db4751f1da5c98c02eaa5eb48944da0a6ec31968ea1f0caecb
Tx public key: 3f7527d9681443dc5aeddda4999609c49dd11280479d7a216ced4ab3e3048f4d
Timestamp: 1727985488 Timestamp [UCT]: 2024-10-03 19:58:08 Age [y:d:h:m:s]: 00:051:21:29:41
Block: 1123769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37061 RingCT/type: yes/0
Extra: 013f7527d9681443dc5aeddda4999609c49dd11280479d7a216ced4ab3e3048f4d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e64309ff03af13d8a5aa71f45b4100d0a93eab6c11b7cf2da565924f74f4596c 0.600000000000 1606304 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": 1123779, "vin": [ { "gen": { "height": 1123769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e64309ff03af13d8a5aa71f45b4100d0a93eab6c11b7cf2da565924f74f4596c" } } ], "extra": [ 1, 63, 117, 39, 217, 104, 20, 67, 220, 90, 237, 221, 164, 153, 150, 9, 196, 157, 209, 18, 128, 71, 157, 122, 33, 108, 237, 74, 179, 227, 4, 143, 77, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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