Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87b346d834ece43b8b1579d2da780d9af71d121c15d4e407c66481c6fc0837a5

Tx prefix hash: e869082c3dd46aea575b3670640c99005d447452fd38f8c462743e5a31f7a18f
Tx public key: 0ef20e0e38c25d23e3ce43f6bd704fcdcb730f7ebfccf02e7b30d680f4aa2b21
Timestamp: 1705384720 Timestamp [UTC]: 2024-01-16 05:58:40 Age [y:d:h:m:s]: 02:095:02:37:58
Block: 936355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579879 RingCT/type: yes/0
Extra: 010ef20e0e38c25d23e3ce43f6bd704fcdcb730f7ebfccf02e7b30d680f4aa2b210211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c5ee159a9bc2d1da39d3c32d35a90b8b57d179553c08621cda7ffb4e14552c15 0.000600000000 1394379 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": 936365, "vin": [ { "gen": { "height": 936355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5ee159a9bc2d1da39d3c32d35a90b8b57d179553c08621cda7ffb4e14552c15" } } ], "extra": [ 1, 14, 242, 14, 14, 56, 194, 93, 35, 227, 206, 67, 246, 189, 112, 79, 205, 203, 115, 15, 126, 191, 204, 240, 46, 123, 48, 214, 128, 244, 170, 43, 33, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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: