Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d2c96e06c313cc8f2976af2d0833e6fe9f806bb3fcfcdab78d977513e5696c

Tx prefix hash: b43d8354013e7df4eb6c335cb61528298b581093d7e906f44b2be5f1edfabb55
Tx public key: bbf232bb445c5abd80331324c3e47aa62881196e84a0e520d80ca151e9d37817
Timestamp: 1772908575 Timestamp [UTC]: 2026-03-07 18:36:15 Age [y:d:h:m:s]: 00:252:14:32:41
Block: 1492832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185955 RingCT/type: yes/0
Extra: 01bbf232bb445c5abd80331324c3e47aa62881196e84a0e520d80ca151e9d37817021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c752172b6d4627a50d87d891a511f5e2b2189b2a3b533672a52296737b7b5b4c 0.000600000000 1982384 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": 1492842, "vin": [ { "gen": { "height": 1492832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c752172b6d4627a50d87d891a511f5e2b2189b2a3b533672a52296737b7b5b4c" } } ], "extra": [ 1, 187, 242, 50, 187, 68, 92, 90, 189, 128, 51, 19, 36, 195, 228, 122, 166, 40, 129, 25, 110, 132, 160, 229, 32, 216, 12, 161, 81, 233, 211, 120, 23, 2, 17, 0, 0, 0, 3, 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: