Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95189b934333a7ca01a20725f28369aec615defc08def46f155e753ea2f46e4e

Tx prefix hash: d618f8a86ae03ad111225837c2a7d1096cb0915949514a18e466bd6d45fa35a3
Tx public key: 9b31ac98d646b1844465b25a737d015d2cd09576f709060c4fbe4445b4121195
Timestamp: 1712875407 Timestamp [UTC]: 2024-04-11 22:43:27 Age [y:d:h:m:s]: 02:032:18:01:42
Block: 998463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535269 RingCT/type: yes/0
Extra: 019b31ac98d646b1844465b25a737d015d2cd09576f709060c4fbe4445b41211950211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8ddfa036a65b829a2d1e03e29866fca1a37290ac7b1a2ef28a0c39d74cf8c35c 0.000600000000 1458913 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": 998473, "vin": [ { "gen": { "height": 998463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ddfa036a65b829a2d1e03e29866fca1a37290ac7b1a2ef28a0c39d74cf8c35c" } } ], "extra": [ 1, 155, 49, 172, 152, 214, 70, 177, 132, 68, 101, 178, 90, 115, 125, 1, 93, 44, 208, 149, 118, 247, 9, 6, 12, 79, 190, 68, 69, 180, 18, 17, 149, 2, 17, 0, 0, 0, 3, 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: