Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a695ddad54d651098541c99317ad7f3e734d12470f7ef2d71dcc4eb1152cbde2

Tx prefix hash: 7e4267434e93f22dcf69339a23fd0eac4f057d4d712a04c380b655f92540f087
Tx public key: e0bd4e4b06f2d6b7f7d7460574cba31115c430f6bc916b6a1ed6acf304ba0866
Timestamp: 1771274144 Timestamp [UTC]: 2026-02-16 20:35:44 Age [y:d:h:m:s]: 00:093:00:35:08
Block: 1479290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59961 RingCT/type: yes/0
Extra: 01e0bd4e4b06f2d6b7f7d7460574cba31115c430f6bc916b6a1ed6acf304ba0866021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b0c16d626e0ebb434426af78af4e0aa55f37aab7334bc517f1e3d7d448b6b0ad 0.000600000000 1968630 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": 1479300, "vin": [ { "gen": { "height": 1479290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0c16d626e0ebb434426af78af4e0aa55f37aab7334bc517f1e3d7d448b6b0ad" } } ], "extra": [ 1, 224, 189, 78, 75, 6, 242, 214, 183, 247, 215, 70, 5, 116, 203, 163, 17, 21, 196, 48, 246, 188, 145, 107, 106, 30, 214, 172, 243, 4, 186, 8, 102, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: