Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdc4e1d93462b0a3938bd976f17c97f08bf0b063e21be62955ca3c9b317cd6c9

Tx prefix hash: 6d651abfa5dc77c4fa9b3a8caa72c49a61177f9ade1d00bdb87cf3bdc700aba0
Tx public key: 61086680a2607ff83ad475cbf1adc04a23155210f818446b26b94f03bfd80d64
Timestamp: 1770318300 Timestamp [UTC]: 2026-02-05 19:05:00 Age [y:d:h:m:s]: 00:284:04:57:22
Block: 1471406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208603 RingCT/type: yes/0
Extra: 0161086680a2607ff83ad475cbf1adc04a23155210f818446b26b94f03bfd80d6402110000000ef188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 55537e41cbcd94f5e6938209da01dc551d1ec5782f93ac15dcd87ffa88dda47b 0.000600000000 1960678 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": 1471416, "vin": [ { "gen": { "height": 1471406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55537e41cbcd94f5e6938209da01dc551d1ec5782f93ac15dcd87ffa88dda47b" } } ], "extra": [ 1, 97, 8, 102, 128, 162, 96, 127, 248, 58, 212, 117, 203, 241, 173, 192, 74, 35, 21, 82, 16, 248, 24, 68, 107, 38, 185, 79, 3, 191, 216, 13, 100, 2, 17, 0, 0, 0, 14, 241, 136, 200, 168, 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: