Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35f64ad97fb2746d39bf77311cd9b085c2e739024bce01ec7fcd32a3ce12779b

Tx prefix hash: fb4b560cb3de12a1658f2ad773babc6120e9ab6ff5ed6c1a178fa646d0658c4a
Tx public key: 1f2dbbfa0948544b819e75ae97a6de97a71d67142286fdbfc7bd0c33ed7f8a6d
Timestamp: 1773690816 Timestamp [UTC]: 2026-03-16 19:53:36 Age [y:d:h:m:s]: 00:244:23:14:46
Block: 1499302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180551 RingCT/type: yes/0
Extra: 011f2dbbfa0948544b819e75ae97a6de97a71d67142286fdbfc7bd0c33ed7f8a6d021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a537a725712996e674901d8bd7c7fceb27d97efe14e10a8fdfbd1dcfb0cca8b2 0.000600000000 1988956 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": 1499312, "vin": [ { "gen": { "height": 1499302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a537a725712996e674901d8bd7c7fceb27d97efe14e10a8fdfbd1dcfb0cca8b2" } } ], "extra": [ 1, 31, 45, 187, 250, 9, 72, 84, 75, 129, 158, 117, 174, 151, 166, 222, 151, 167, 29, 103, 20, 34, 134, 253, 191, 199, 189, 12, 51, 237, 127, 138, 109, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: