Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b5561dec45e7a566c35081a3b2ab44cd5ce6e4f9764bdc87abbc4f50bcbb729

Tx prefix hash: 71e8ce219b4e20b1fbdff1a5f77b606f9fde1dd17d1a5407019d10ce5d3f8ca3
Tx public key: 22c24d25a7581334e924465351273d17e72741ddfa7360476c485747c766ab0e
Timestamp: 1748500322 Timestamp [UTC]: 2025-05-29 06:32:02 Age [y:d:h:m:s]: 00:259:13:14:03
Block: 1293310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183102 RingCT/type: yes/0
Extra: 0122c24d25a7581334e924465351273d17e72741ddfa7360476c485747c766ab0e021100000004df096e52000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 03ce211d37fc8f86623252e98ae14dffdd1d2ca0cd853c602ea9ef56b34f6c86 0.000600000000 1780781 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": 1293320, "vin": [ { "gen": { "height": 1293310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03ce211d37fc8f86623252e98ae14dffdd1d2ca0cd853c602ea9ef56b34f6c86" } } ], "extra": [ 1, 34, 194, 77, 37, 167, 88, 19, 52, 233, 36, 70, 83, 81, 39, 61, 23, 231, 39, 65, 221, 250, 115, 96, 71, 108, 72, 87, 71, 199, 102, 171, 14, 2, 17, 0, 0, 0, 4, 223, 9, 110, 82, 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) | dinastycoin version: tesla-369