Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb2fd1e68e6debedc5bbd97bc9f38e1782b947414b0f119515640e95fd7c783a

Tx prefix hash: b2c8f14027a7dc62d3d5f20a1b2e597d34143addccae45d4dddd45813a8f0072
Tx public key: 6a43367f9ee73c2a501ea7b2632045b9e765d34aeb2a97e8819896b467dcea39
Timestamp: 1771830621 Timestamp [UTC]: 2026-02-23 07:10:21 Age [y:d:h:m:s]: 00:269:08:05:15
Block: 1483907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198066 RingCT/type: yes/0
Extra: 016a43367f9ee73c2a501ea7b2632045b9e765d34aeb2a97e8819896b467dcea3902110000000ae4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3f470f509dd26cdeae05cae2f0d95362979ad1d83a27ad2eef62aae7ca3f7532 0.000600000000 1973319 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": 1483917, "vin": [ { "gen": { "height": 1483907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f470f509dd26cdeae05cae2f0d95362979ad1d83a27ad2eef62aae7ca3f7532" } } ], "extra": [ 1, 106, 67, 54, 127, 158, 231, 60, 42, 80, 30, 167, 178, 99, 32, 69, 185, 231, 101, 211, 74, 235, 42, 151, 232, 129, 152, 150, 180, 103, 220, 234, 57, 2, 17, 0, 0, 0, 10, 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: