Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16075ee2d5db24796ea4ad0c6bfb45a6372e4f97d1277186de42e2c2ed60164d

Tx prefix hash: b752767b672b5a4e168bc31026bccf4cc9c38ff15dda5100a5790a54a699ab03
Tx public key: bb1da570b8ef91e686a9305d7b459d5ff72aa1849215305e273f54e9d7916563
Timestamp: 1772072928 Timestamp [UTC]: 2026-02-26 02:28:48 Age [y:d:h:m:s]: 00:267:13:29:59
Block: 1485942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196863 RingCT/type: yes/0
Extra: 01bb1da570b8ef91e686a9305d7b459d5ff72aa1849215305e273f54e9d7916563021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ea0d4afcec06fb8dccb75edfd8908945741820cbf67acfece5f11b88789aa01a 0.000600000000 1975382 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": 1485952, "vin": [ { "gen": { "height": 1485942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea0d4afcec06fb8dccb75edfd8908945741820cbf67acfece5f11b88789aa01a" } } ], "extra": [ 1, 187, 29, 165, 112, 184, 239, 145, 230, 134, 169, 48, 93, 123, 69, 157, 95, 247, 42, 161, 132, 146, 21, 48, 94, 39, 63, 84, 233, 215, 145, 101, 99, 2, 17, 0, 0, 0, 6, 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: