Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3eb9bad7ce9bd422f60feb90ec3bb16d2cf9a7b33b168ab4ff54da71fdf5e7

Tx prefix hash: 28ac34c19a8978c96536cd27ab9abe01ced7674e58d5cf6c1a89745cd8ebdd16
Tx public key: f4829f9d615656d3892c215770aeafeb3bf8ac030197b858196d3ed25a11f4ef
Timestamp: 1744726716 Timestamp [UTC]: 2025-04-15 14:18:36 Age [y:d:h:m:s]: 01:213:02:09:54
Block: 1262041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416218 RingCT/type: yes/0
Extra: 01f4829f9d615656d3892c215770aeafeb3bf8ac030197b858196d3ed25a11f4ef02110000000ddbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3035bf3fc053699f5c5ca392c8af05ab2135456eea35a15d7ff5f54a2e1e32cd 0.000600000000 1749218 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": 1262051, "vin": [ { "gen": { "height": 1262041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3035bf3fc053699f5c5ca392c8af05ab2135456eea35a15d7ff5f54a2e1e32cd" } } ], "extra": [ 1, 244, 130, 159, 157, 97, 86, 86, 211, 137, 44, 33, 87, 112, 174, 175, 235, 59, 248, 172, 3, 1, 151, 184, 88, 25, 109, 62, 210, 90, 17, 244, 239, 2, 17, 0, 0, 0, 13, 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: