Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f432ca16d1f1ef720e5183b1789a69cf32de5a294ffb4f694dfe8a46ed08deef

Tx prefix hash: bc6a4012dcbc92629f54d51771234f7e86395193c75edb311f70f2afb2dfddfb
Tx public key: 1c53faacf13f20806edfadacf75cab2bd4ab1aa7819427989b69f6d32bfc57ea
Timestamp: 1716579933 Timestamp [UTC]: 2024-05-24 19:45:33 Age [y:d:h:m:s]: 02:181:04:35:37
Block: 1029203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 654291 RingCT/type: yes/0
Extra: 011c53faacf13f20806edfadacf75cab2bd4ab1aa7819427989b69f6d32bfc57ea02110000000552d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e6894719be269f5a4d330e53746ee97d61e794412eb4f9f9e2a3fbbff11f554b 0.000600000000 1497228 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": 1029213, "vin": [ { "gen": { "height": 1029203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6894719be269f5a4d330e53746ee97d61e794412eb4f9f9e2a3fbbff11f554b" } } ], "extra": [ 1, 28, 83, 250, 172, 241, 63, 32, 128, 110, 223, 173, 172, 247, 92, 171, 43, 212, 171, 26, 167, 129, 148, 39, 152, 155, 105, 246, 211, 43, 252, 87, 234, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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: