Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea7a862746580dafc2f8a2cdfcc721ce725e7c2ee6e1c956a4dd0685d10838f

Tx prefix hash: 776dd6ac06ce14077237834cccefdaccb14a8ed4dcd3cebd922caacf2dd194a6
Tx public key: 1034ae76a082265f0cf262150996f5e3638230ac984e50e4f1e99d77b02199cd
Timestamp: 1731263638 Timestamp [UTC]: 2024-11-10 18:33:58 Age [y:d:h:m:s]: 02:009:21:49:24
Block: 1150850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531968 RingCT/type: yes/0
Extra: 011034ae76a082265f0cf262150996f5e3638230ac984e50e4f1e99d77b02199cd021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9d4587afb0eeba0db27d9a40eb25ec86e25af73636a34f3be2899361fce12063 0.000600000000 1636267 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": 1150860, "vin": [ { "gen": { "height": 1150850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d4587afb0eeba0db27d9a40eb25ec86e25af73636a34f3be2899361fce12063" } } ], "extra": [ 1, 16, 52, 174, 118, 160, 130, 38, 95, 12, 242, 98, 21, 9, 150, 245, 227, 99, 130, 48, 172, 152, 78, 80, 228, 241, 233, 157, 119, 176, 33, 153, 205, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: