Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2494ca6da0cbfeaca23cf7944cdf06b8233f5be46d9cc7f09832bc0440c0fe96

Tx prefix hash: 3c576661c011a50ffc8095eebd5a9b5a1eeb39650da45b1b3f2b733d7b8c225a
Tx public key: a778cf2a0ff66d4f5d2c5ad0780632c0e9dea4bf38f387804e469339b8224265
Timestamp: 1733388192 Timestamp [UCT]: 2024-12-05 08:43:12 Age [y:d:h:m:s]: 00:100:06:03:51
Block: 1168450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71459 RingCT/type: yes/0
Extra: 01a778cf2a0ff66d4f5d2c5ad0780632c0e9dea4bf38f387804e469339b82242650211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 475d28a680941ac7a09bc5f45b90aa03e10ed684ab5d7f9ff2c26072c3e67711 0.600000000000 1654159 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": 1168460, "vin": [ { "gen": { "height": 1168450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "475d28a680941ac7a09bc5f45b90aa03e10ed684ab5d7f9ff2c26072c3e67711" } } ], "extra": [ 1, 167, 120, 207, 42, 15, 246, 109, 79, 93, 44, 90, 208, 120, 6, 50, 192, 233, 222, 164, 191, 56, 243, 135, 128, 78, 70, 147, 57, 184, 34, 66, 101, 2, 17, 0, 0, 0, 4, 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