Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ed99ecb2849191efbd30a804d30f5da8c8951130d04e46d04de32f61bdde826

Tx prefix hash: db68008ee9a12a82b1309d9a7e7dfdc8516dd6ce4ad2138da0a276dbeb86dce9
Tx public key: ef0b2192a470662d2389b7c6a1926629e030452a150923c586fe3c366511bfb1
Timestamp: 1739172447 Timestamp [UTC]: 2025-02-10 07:27:27 Age [y:d:h:m:s]: 01:100:07:16:11
Block: 1216069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323730 RingCT/type: yes/0
Extra: 01ef0b2192a470662d2389b7c6a1926629e030452a150923c586fe3c366511bfb10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: de4d6978685c34781175c23a72ac6ec69ad072f8c825dcd624b9d053c0932ec9 0.000600000000 1702870 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": 1216079, "vin": [ { "gen": { "height": 1216069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de4d6978685c34781175c23a72ac6ec69ad072f8c825dcd624b9d053c0932ec9" } } ], "extra": [ 1, 239, 11, 33, 146, 164, 112, 102, 45, 35, 137, 183, 198, 161, 146, 102, 41, 224, 48, 69, 42, 21, 9, 35, 197, 134, 254, 60, 54, 101, 17, 191, 177, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: