Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef32b3ecc209811cb66ebfaaa8da839a6cef4a2fc0c651ee41fd67f50b1d5c3

Tx prefix hash: 824703d2919451f7d2299d1eefc82ab360400ced23b4f2c2feebc0e7e08bc00c
Tx public key: f79c981c2905cb90139f62187c88a3d3e986c9f6c06946a7ee2a03e8cbe37b5e
Timestamp: 1710647387 Timestamp [UTC]: 2024-03-17 03:49:47 Age [y:d:h:m:s]: 02:248:18:09:31
Block: 980034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 702927 RingCT/type: yes/0
Extra: 01f79c981c2905cb90139f62187c88a3d3e986c9f6c06946a7ee2a03e8cbe37b5e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5540681522c291d9b5a196f51b14507d02efb0b1531e3ce00962f99ee4d7724a 0.000600000000 1440093 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 dinastycoin-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": 980044, "vin": [ { "gen": { "height": 980034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5540681522c291d9b5a196f51b14507d02efb0b1531e3ce00962f99ee4d7724a" } } ], "extra": [ 1, 247, 156, 152, 28, 41, 5, 203, 144, 19, 159, 98, 24, 124, 136, 163, 211, 233, 134, 201, 246, 192, 105, 70, 167, 238, 42, 3, 232, 203, 227, 123, 94, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: