Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a926329bb8022dc7bfb41973e138f5b323cdd2c62a23ade224de4626652b7fe5

Tx prefix hash: 241b7f2cb6f1e6d98ba8c1ed64254ddcdd1149edf62d88a35804dfce3ff4c11a
Tx public key: 4e40c7cb9980d31152aebb9c823639388b71eb03c352cee2fb4801903816e306
Timestamp: 1736410493 Timestamp [UCT]: 2025-01-09 08:14:53 Age [y:d:h:m:s]: 00:162:09:17:24
Block: 1193464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115730 RingCT/type: yes/0
Extra: 014e40c7cb9980d31152aebb9c823639388b71eb03c352cee2fb4801903816e3060211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee85b096919a4ced2dc6c3d91968bca72b9d94d4c1f2fa81795d2e767978a75b 0.600000000000 1680025 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": 1193474, "vin": [ { "gen": { "height": 1193464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee85b096919a4ced2dc6c3d91968bca72b9d94d4c1f2fa81795d2e767978a75b" } } ], "extra": [ 1, 78, 64, 199, 203, 153, 128, 211, 17, 82, 174, 187, 156, 130, 54, 57, 56, 139, 113, 235, 3, 195, 82, 206, 226, 251, 72, 1, 144, 56, 22, 227, 6, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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