Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 511d908be92f88873912ec8f01646e09ca80ac7669813dc825fdec46c2a16ff8

Tx prefix hash: c2efa0beae84fd7861030546e2479778a84acef78045e5e5ce1e760b117c10e6
Tx public key: 88f21a7986a9a0a632bac89c8ed6309d1e5f39145046c45b1be8448f684eeef3
Timestamp: 1705270768 Timestamp [UTC]: 2024-01-14 22:19:28 Age [y:d:h:m:s]: 02:122:21:35:04
Block: 935426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599904 RingCT/type: yes/0
Extra: 0188f21a7986a9a0a632bac89c8ed6309d1e5f39145046c45b1be8448f684eeef30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0c74b91b210cb75dee43acb28384183b0a0cf7dd815b2b0f44123cc9e5e12496 0.000600000000 1393442 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": 935436, "vin": [ { "gen": { "height": 935426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c74b91b210cb75dee43acb28384183b0a0cf7dd815b2b0f44123cc9e5e12496" } } ], "extra": [ 1, 136, 242, 26, 121, 134, 169, 160, 166, 50, 186, 200, 156, 142, 214, 48, 157, 30, 95, 57, 20, 80, 70, 196, 91, 27, 232, 68, 143, 104, 78, 238, 243, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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: