Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 941d4ca96ae67006b8af3c4ee2d6c33bae18d9b94e95e6fae1138a97d4cdd901

Tx prefix hash: 78064a545eb33c1c51874b4d9dae36ed59974395b1fe1a2fb6cfa85725ab29a6
Tx public key: 95f6c953aa58093df833efccd319bde26eed56ac0e1af51adc82569ef8657533
Timestamp: 1761286955 Timestamp [UTC]: 2025-10-24 06:22:35 Age [y:d:h:m:s]: 01:022:12:56:53
Block: 1396736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282371 RingCT/type: yes/0
Extra: 0195f6c953aa58093df833efccd319bde26eed56ac0e1af51adc82569ef8657533021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ab31b991a5a3d3dc50a3d4a6ee3b2483b8b33af39ead1f8680b2e7a212756281 0.000600000000 1885023 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": 1396746, "vin": [ { "gen": { "height": 1396736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab31b991a5a3d3dc50a3d4a6ee3b2483b8b33af39ead1f8680b2e7a212756281" } } ], "extra": [ 1, 149, 246, 201, 83, 170, 88, 9, 61, 248, 51, 239, 204, 211, 25, 189, 226, 110, 237, 86, 172, 14, 26, 245, 26, 220, 130, 86, 158, 248, 101, 117, 51, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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: