Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc9f0713420c95f3cd3a7e0ab1f2299b461c02a80d847ec9b83ebebb1f3f3b03

Tx prefix hash: 9f06f632ef9d9830ff1139f5265f897faea5d9f3df5dbb99a90ec45f2db2af1e
Tx public key: 6ef8427b462388e8cad94cf481771e3778960e312bc4d55095ded85c96dc2d4f
Timestamp: 1738454919 Timestamp [UTC]: 2025-02-02 00:08:39 Age [y:d:h:m:s]: 01:290:16:07:28
Block: 1210123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471880 RingCT/type: yes/0
Extra: 016ef8427b462388e8cad94cf481771e3778960e312bc4d55095ded85c96dc2d4f021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fd85ca40a07ae472be681efebf4aec3411e4a1a81d86cfa0be8b16e96a273735 0.000600000000 1696874 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": 1210133, "vin": [ { "gen": { "height": 1210123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd85ca40a07ae472be681efebf4aec3411e4a1a81d86cfa0be8b16e96a273735" } } ], "extra": [ 1, 110, 248, 66, 123, 70, 35, 136, 232, 202, 217, 76, 244, 129, 119, 30, 55, 120, 150, 14, 49, 43, 196, 213, 80, 149, 222, 216, 92, 150, 220, 45, 79, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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: