Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bce9d40fa2b4412385df691c13f8a6733ad0ef6ef716c0b67cd8d3746f8f763

Tx prefix hash: 7660d8aea873b6ad69783bc1d7b20596c047fff38f2a2b2c8f7c31ceadba2f63
Tx public key: d4defaad07849e0511689aa1b1bafb951f75a94f38e38d45e830543924a95987
Timestamp: 1744218225 Timestamp [UTC]: 2025-04-09 17:03:45 Age [y:d:h:m:s]: 01:220:03:44:38
Block: 1257833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421321 RingCT/type: yes/0
Extra: 01d4defaad07849e0511689aa1b1bafb951f75a94f38e38d45e830543924a95987021100000002dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e56966f63cc1d2ec81215b115af081df8a4e84d974752e31ba88c316a18474df 0.000600000000 1744964 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": 1257843, "vin": [ { "gen": { "height": 1257833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e56966f63cc1d2ec81215b115af081df8a4e84d974752e31ba88c316a18474df" } } ], "extra": [ 1, 212, 222, 250, 173, 7, 132, 158, 5, 17, 104, 154, 161, 177, 186, 251, 149, 31, 117, 169, 79, 56, 227, 141, 69, 232, 48, 84, 57, 36, 169, 89, 135, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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: