Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 691ba99ed7fd60968488e9e1e4dca0afbac01cc101f87a5235812ed0bc5b3aa5

Tx prefix hash: be45cfdea075b96d1502211797eeef2122f10c40bce3cd95b0daf6c45e3e3858
Tx public key: f30ea65b9a1626ef83376fc3f07f13df9bff9f244984db7aa277db3602e292a5
Timestamp: 1773718279 Timestamp [UTC]: 2026-03-17 03:31:19 Age [y:d:h:m:s]: 00:244:15:28:39
Block: 1499532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180316 RingCT/type: yes/0
Extra: 01f30ea65b9a1626ef83376fc3f07f13df9bff9f244984db7aa277db3602e292a5021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dcc512df9bcececf3033d8ae5e53f219ec51e01a11092e86e4747821e91b3879 0.000600000000 1989194 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": 1499542, "vin": [ { "gen": { "height": 1499532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcc512df9bcececf3033d8ae5e53f219ec51e01a11092e86e4747821e91b3879" } } ], "extra": [ 1, 243, 14, 166, 91, 154, 22, 38, 239, 131, 55, 111, 195, 240, 127, 19, 223, 155, 255, 159, 36, 73, 132, 219, 122, 162, 119, 219, 54, 2, 226, 146, 165, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: