Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbde2630d26df2ee2d3f37be5b98d52988f3b5e829bb134114b873bfc6e2d159

Tx prefix hash: a2c658b596c8b369c98d2f56a7f6f3108e230a1cfdd9e599236ee4ecfcb8e51c
Tx public key: 616279d555833d0e51265158fc65b62582f25d1298c39d5d0cca2e2c0397f8b9
Timestamp: 1773879341 Timestamp [UTC]: 2026-03-19 00:15:41 Age [y:d:h:m:s]: 00:240:21:37:05
Block: 1500835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177594 RingCT/type: yes/0
Extra: 01616279d555833d0e51265158fc65b62582f25d1298c39d5d0cca2e2c0397f8b9021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 40253f5d1ea0a5663b1187393183cda76fbeedd5b6eb5f786f70926373675fa3 0.000600000000 1990511 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": 1500845, "vin": [ { "gen": { "height": 1500835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40253f5d1ea0a5663b1187393183cda76fbeedd5b6eb5f786f70926373675fa3" } } ], "extra": [ 1, 97, 98, 121, 213, 85, 131, 61, 14, 81, 38, 81, 88, 252, 101, 182, 37, 130, 242, 93, 18, 152, 195, 157, 93, 12, 202, 46, 44, 3, 151, 248, 185, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 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: