Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2cd581d46e22fbe6f7176dcb70f242599a66e0663d4e8172f705ef72636e2fc

Tx prefix hash: b38ed1c8ace617f906ea97e019019644b010f9b2e6bd59116fe9d4400276e80b
Tx public key: 762af18b7eada26325b75ea8d297df0cb7af5fc24b18a4ce2f6ea0b565b50ace
Timestamp: 1724952786 Timestamp [UCT]: 2024-08-29 17:33:06 Age [y:d:h:m:s]: 00:220:02:55:23
Block: 1098610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157171 RingCT/type: yes/0
Extra: 01762af18b7eada26325b75ea8d297df0cb7af5fc24b18a4ce2f6ea0b565b50ace021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a2be164358f622e3deee5906ce2bcb9939de11c55694b7a1f7d329616757483 0.600000000000 1574387 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": 1098620, "vin": [ { "gen": { "height": 1098610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2be164358f622e3deee5906ce2bcb9939de11c55694b7a1f7d329616757483" } } ], "extra": [ 1, 118, 42, 241, 139, 126, 173, 162, 99, 37, 183, 94, 168, 210, 151, 223, 12, 183, 175, 95, 194, 75, 24, 164, 206, 47, 110, 160, 181, 101, 181, 10, 206, 2, 17, 0, 0, 0, 2, 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