Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd966a1f166a2248ce5227679c5faa4f173ac40ef8f568606473bd7662a40710

Tx prefix hash: 022a5d1da1a8ac2a17cb112fd566daf7e258ee53497d4c8d7213738fe4e35c7c
Tx public key: 4b23fd27f30ba95de00adac1f0941eca8dc653c884cf9dce7ab26926f44cda78
Timestamp: 1577813653 Timestamp [UTC]: 2019-12-31 17:34:13 Age [y:d:h:m:s]: 06:268:09:05:58
Block: 35916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1606324 RingCT/type: yes/0
Extra: 014b23fd27f30ba95de00adac1f0941eca8dc653c884cf9dce7ab26926f44cda780211000000acfeadaf7f000000000000000000

1 output(s) for total of 0.466655336017 xmr

stealth address amount amount idx tag
00: 2b2206c07bec606cb78ec7db84b7913351286e5e41697c194dcc13f9569e210b 0.466655336017 60658 of 0 -

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": 35926, "vin": [ { "gen": { "height": 35916 } } ], "vout": [ { "amount": 466655336017, "target": { "key": "2b2206c07bec606cb78ec7db84b7913351286e5e41697c194dcc13f9569e210b" } } ], "extra": [ 1, 75, 35, 253, 39, 243, 11, 169, 93, 224, 10, 218, 193, 240, 148, 30, 202, 141, 198, 83, 200, 132, 207, 157, 206, 122, 178, 105, 38, 244, 76, 218, 120, 2, 17, 0, 0, 0, 172, 254, 173, 175, 127, 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: