Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: affe7bb68eeefab291116ec7939bdfe16a334a35f087175c583734ce9910e737

Tx prefix hash: a293514a9b0ef57dc8c5371167c5bee01ddf91d7cf2e9ee1888f3d0682521773
Tx public key: 8ca778997a5d92fcb14bd813685c0b85de9e4fd7ed513cc4d558e9325aa8c2bd
Timestamp: 1764632707 Timestamp [UTC]: 2025-12-01 23:45:07 Age [y:d:h:m:s]: 00:353:16:04:21
Block: 1424454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258347 RingCT/type: yes/0
Extra: 018ca778997a5d92fcb14bd813685c0b85de9e4fd7ed513cc4d558e9325aa8c2bd021100000001da554848000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 07c6c6717f836c45aa54a99f05fce6e9b1c575fa379b308780e4aad8f92e6524 0.000600000000 1913085 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": 1424464, "vin": [ { "gen": { "height": 1424454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07c6c6717f836c45aa54a99f05fce6e9b1c575fa379b308780e4aad8f92e6524" } } ], "extra": [ 1, 140, 167, 120, 153, 122, 93, 146, 252, 177, 75, 216, 19, 104, 92, 11, 133, 222, 158, 79, 215, 237, 81, 60, 196, 213, 88, 233, 50, 90, 168, 194, 189, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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: