Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f71ddfe8395b68c886dc339ba875aea9a48707392b9beebfd42d2af9b5bc89fe

Tx prefix hash: b54c603f415da001efd2e8444c6eafca3a80dc9025af16fd6ff4a3e19438e8dc
Tx public key: 6c5541d880472cc5e85a219375c14d9f24a72762227c43f5a24fe50ff01c4565
Timestamp: 1770814327 Timestamp [UTC]: 2026-02-11 12:52:07 Age [y:d:h:m:s]: 00:276:19:37:15
Block: 1475507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 203263 RingCT/type: yes/0
Extra: 016c5541d880472cc5e85a219375c14d9f24a72762227c43f5a24fe50ff01c456502084e0b2627d006dd90

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0150fd2fc2d2d2e97a5843a9f6d8f8774d488eacb145cec24c7ca11ae0706c09 0.000600000000 1964809 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": 1475517, "vin": [ { "gen": { "height": 1475507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0150fd2fc2d2d2e97a5843a9f6d8f8774d488eacb145cec24c7ca11ae0706c09" } } ], "extra": [ 1, 108, 85, 65, 216, 128, 71, 44, 197, 232, 90, 33, 147, 117, 193, 77, 159, 36, 167, 39, 98, 34, 124, 67, 245, 162, 79, 229, 15, 240, 28, 69, 101, 2, 8, 78, 11, 38, 39, 208, 6, 221, 144 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: