Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a262cb9cfe3b0adaad17070f8627cc14ba28dda2b3b379eb3e2f11196dcd72e7

Tx prefix hash: 9651526ee4a8d1ad671efff05e435711c4db8ea5ad72dd07f405593e4d533f1d
Tx public key: 7a61d9e417e8e8b0e6914a09d1286083d251d2c394e7bc78bbf0474d9dbecd3b
Timestamp: 1737873401 Timestamp [UCT]: 2025-01-26 06:36:41 Age [y:d:h:m:s]: 00:325:08:16:08
Block: 1205535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230107 RingCT/type: yes/0
Extra: 017a61d9e417e8e8b0e6914a09d1286083d251d2c394e7bc78bbf0474d9dbecd3b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fe43c73eb5f798c36411af95546041510c9dcce1fa2167e3e6937b7e079d572 0.600000000000 1692232 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": 1205545, "vin": [ { "gen": { "height": 1205535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fe43c73eb5f798c36411af95546041510c9dcce1fa2167e3e6937b7e079d572" } } ], "extra": [ 1, 122, 97, 217, 228, 23, 232, 232, 176, 230, 145, 74, 9, 209, 40, 96, 131, 210, 81, 210, 195, 148, 231, 188, 120, 187, 240, 71, 77, 157, 190, 205, 59, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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