Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2adeebd9b5156763070e8dba4e5d39c1d8b0c879d34a975b1b48ba4141b9603a

Tx prefix hash: 981afeda4da9a03e98ff70f7843d245db81e5cd6473be2226597f2ae75f0925b
Tx public key: b94034e118b28d6570c7b5f9fd334534dde0aa2981264791d375c73a8dad68c4
Timestamp: 1747176290 Timestamp [UTC]: 2025-05-13 22:44:50 Age [y:d:h:m:s]: 01:067:23:14:21
Block: 1282327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300787 RingCT/type: yes/0
Extra: 01b94034e118b28d6570c7b5f9fd334534dde0aa2981264791d375c73a8dad68c40211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 651a7a4a2955e2d39360081d75c60cef86b707f3975f2b09557f2d6d3059aa22 0.000600000000 1769734 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": 1282337, "vin": [ { "gen": { "height": 1282327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651a7a4a2955e2d39360081d75c60cef86b707f3975f2b09557f2d6d3059aa22" } } ], "extra": [ 1, 185, 64, 52, 225, 24, 178, 141, 101, 112, 199, 181, 249, 253, 51, 69, 52, 221, 224, 170, 41, 129, 38, 71, 145, 211, 117, 199, 58, 141, 173, 104, 196, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: