Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71938fc3867eb0dd0d3de39e7dd47873ce795ba559efa775df94e41c6dd7ddb0

Tx prefix hash: 0cbe75c9f1ae04b12af8de6b4de228589f08abfa6fc24fcc7ca8371542e122df
Tx public key: b307a5dc1c7ee8f5552e75631dfa64e4f178ce2263dd6298f447928693555c7d
Timestamp: 1744292279 Timestamp [UTC]: 2025-04-10 13:37:59 Age [y:d:h:m:s]: 01:219:03:10:07
Block: 1258453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420573 RingCT/type: yes/0
Extra: 01b307a5dc1c7ee8f5552e75631dfa64e4f178ce2263dd6298f447928693555c7d021100000008dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 04be9b687b9dafd0c49ff64c7cdc9c077cce327d118f7aa1e29560b1eb6f8544 0.000600000000 1745586 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": 1258463, "vin": [ { "gen": { "height": 1258453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04be9b687b9dafd0c49ff64c7cdc9c077cce327d118f7aa1e29560b1eb6f8544" } } ], "extra": [ 1, 179, 7, 165, 220, 28, 126, 232, 245, 85, 46, 117, 99, 29, 250, 100, 228, 241, 120, 206, 34, 99, 221, 98, 152, 244, 71, 146, 134, 147, 85, 92, 125, 2, 17, 0, 0, 0, 8, 219, 181, 113, 193, 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: