Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc00a657568ec81f39185d641527a6c4ec657bfe07c6d6681bd55684e962a789

Tx prefix hash: f55719fdfb19a2871fbd70e5127c0e0125d3471e2e109086ba4d2615555e7537
Tx public key: 642461b8d6c2276edf85e3dcf5463976a6f1076663789a1e4f41bd4eca2cb34b
Timestamp: 1731445345 Timestamp [UTC]: 2024-11-12 21:02:25 Age [y:d:h:m:s]: 02:003:07:18:28
Block: 1152340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527052 RingCT/type: yes/0
Extra: 01642461b8d6c2276edf85e3dcf5463976a6f1076663789a1e4f41bd4eca2cb34b021100000003d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 651d498fb9664635331b8dcb4f81716663afb9d2c776b9ab731df47a0285ad1a 0.000600000000 1637937 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": 1152350, "vin": [ { "gen": { "height": 1152340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651d498fb9664635331b8dcb4f81716663afb9d2c776b9ab731df47a0285ad1a" } } ], "extra": [ 1, 100, 36, 97, 184, 214, 194, 39, 110, 223, 133, 227, 220, 245, 70, 57, 118, 166, 241, 7, 102, 99, 120, 154, 30, 79, 65, 189, 78, 202, 44, 179, 75, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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: