Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1dd0700a5cc5d454f0fe3a835282a6d6c2f9dd2315ab78578e32e9da71e229

Tx prefix hash: 44bf2d0a523835a3e2dd9f594d130fc5bf89b9427a374d6edd77b51fda896114
Tx public key: a0321a00c2e8b41776c8120bb9ea2b61e84c5c24de2744247855cfef73bfaaf1
Timestamp: 1733354193 Timestamp [UCT]: 2024-12-04 23:16:33 Age [y:d:h:m:s]: 00:115:20:44:02
Block: 1168165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82601 RingCT/type: yes/0
Extra: 01a0321a00c2e8b41776c8120bb9ea2b61e84c5c24de2744247855cfef73bfaaf10211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e691be781ccb093dd4b769cd39bf3c752bf6ba086ec4ed8bcf725ae4a047563b 0.600000000000 1653872 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": 1168175, "vin": [ { "gen": { "height": 1168165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e691be781ccb093dd4b769cd39bf3c752bf6ba086ec4ed8bcf725ae4a047563b" } } ], "extra": [ 1, 160, 50, 26, 0, 194, 232, 180, 23, 118, 200, 18, 11, 185, 234, 43, 97, 232, 76, 92, 36, 222, 39, 68, 36, 120, 85, 207, 239, 115, 191, 170, 241, 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