Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79e7cc7026cf5bb02da679de9fefb1d7a7ac8a350d305f538a44fc453ef0fd9d

Tx prefix hash: 66f2c298f97e98d0ab0cb20fed40ee7ca92810bd9b57f1616d95a2963334ef88
Tx public key: baa25b769cdb8ca523b7be471528e95b29cdbd9012b93f27c50ce2796d0faba6
Timestamp: 1742828170 Timestamp [UTC]: 2025-03-24 14:56:10 Age [y:d:h:m:s]: 01:124:12:47:15
Block: 1246330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352886 RingCT/type: yes/0
Extra: 01baa25b769cdb8ca523b7be471528e95b29cdbd9012b93f27c50ce2796d0faba6021100000008c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2e5f2fbab1611b404ae2330a7cf3761c7e5d279115f671912802ce503d9d860 0.000600000000 1733331 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": 1246340, "vin": [ { "gen": { "height": 1246330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2e5f2fbab1611b404ae2330a7cf3761c7e5d279115f671912802ce503d9d860" } } ], "extra": [ 1, 186, 162, 91, 118, 156, 219, 140, 165, 35, 183, 190, 71, 21, 40, 233, 91, 41, 205, 189, 144, 18, 185, 63, 39, 197, 12, 226, 121, 109, 15, 171, 166, 2, 17, 0, 0, 0, 8, 198, 116, 9, 88, 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: