Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a90cf6e98ca63c14370ad888dd1fec88816a62aaaae8f1affe8a22116ce0ff

Tx prefix hash: 6802aada8acff75ead68f9f867ac64fe91df21f35c2753571e12528b925cace0
Tx public key: 0c0ce90858cdcec0b328c8b796e0203aaee4ccbeb87486e4beb0908abfd26ef5
Timestamp: 1764848874 Timestamp [UTC]: 2025-12-04 11:47:54 Age [y:d:h:m:s]: 00:348:12:23:49
Block: 1426258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254486 RingCT/type: yes/0
Extra: 010c0ce90858cdcec0b328c8b796e0203aaee4ccbeb87486e4beb0908abfd26ef502110000000270609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b3a386f7c6c9592bed94094b40f501c5f5e4166cd8e8ea857a7d869a27994d93 0.000600000000 1914947 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": 1426268, "vin": [ { "gen": { "height": 1426258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3a386f7c6c9592bed94094b40f501c5f5e4166cd8e8ea857a7d869a27994d93" } } ], "extra": [ 1, 12, 12, 233, 8, 88, 205, 206, 192, 179, 40, 200, 183, 150, 224, 32, 58, 174, 228, 204, 190, 184, 116, 134, 228, 190, 176, 144, 138, 191, 210, 110, 245, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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: