Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97f4d92b00a4c2403afb369711990a1fb63f37e4fb3138e7d3404731bee58db0

Tx prefix hash: 9a067cb06cfb8bdc9ff7f92eadfa68c7273fd329ffc64e0124abb8905d967026
Tx public key: 408cab9b802569114ee98603aea7b720a8ede638ac9dbf996e7a9e5083ccd6b2
Timestamp: 1757775025 Timestamp [UTC]: 2025-09-13 14:50:25 Age [y:d:h:m:s]: 00:321:11:21:39
Block: 1367615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235617 RingCT/type: yes/0
Extra: 01408cab9b802569114ee98603aea7b720a8ede638ac9dbf996e7a9e5083ccd6b2021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b4bb8ba80549569d5ae6a676b47bb5295306174b339d4038cc52020b24385845 0.000600000000 1855654 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": 1367625, "vin": [ { "gen": { "height": 1367615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4bb8ba80549569d5ae6a676b47bb5295306174b339d4038cc52020b24385845" } } ], "extra": [ 1, 64, 140, 171, 155, 128, 37, 105, 17, 78, 233, 134, 3, 174, 167, 183, 32, 168, 237, 230, 56, 172, 157, 191, 153, 110, 122, 158, 80, 131, 204, 214, 178, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: