Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38b3c440a10474c423f165e2f52cf39c1b17ba3fe594729fac1164f3209762c0

Tx prefix hash: a29eff76f46ae85e23e019919e011c7739db5c2390b106827050df1deab25371
Tx public key: a3289b5025a5b4f8b18fbcd8acce8b30ed6b263a73cc1d2dd5cddeb0f1f7d07d
Timestamp: 1715327829 Timestamp [UCT]: 2024-05-10 07:57:09 Age [y:d:h:m:s]: 00:229:10:03:12
Block: 1018824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164211 RingCT/type: yes/0
Extra: 01a3289b5025a5b4f8b18fbcd8acce8b30ed6b263a73cc1d2dd5cddeb0f1f7d07d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8acae71689c6e1881f3ea0cba769145ef2b127117db80d925421a4ced1cd75c 0.600000000000 1482619 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": 1018834, "vin": [ { "gen": { "height": 1018824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8acae71689c6e1881f3ea0cba769145ef2b127117db80d925421a4ced1cd75c" } } ], "extra": [ 1, 163, 40, 155, 80, 37, 165, 180, 248, 177, 143, 188, 216, 172, 206, 139, 48, 237, 107, 38, 58, 115, 204, 29, 45, 213, 205, 222, 176, 241, 247, 208, 125, 2, 17, 0, 0, 0, 1, 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