Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05d855fc4f7b6e9cdea431053312e24d8632fa4fa39cc18a3b23c0266a8a8826

Tx prefix hash: 842d1707d8de991f396b2786ab028ed8370b3011601b67befe7907490bbbd57b
Tx public key: 871b9a9890cf0edb95cac75d2d4f96bb1f1a8056e6c96ef36cb538b6ce1d9015
Timestamp: 1577477731 Timestamp [UTC]: 2019-12-27 20:15:31 Age [y:d:h:m:s]: 06:329:11:21:40
Block: 33066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1649449 RingCT/type: yes/0
Extra: 01871b9a9890cf0edb95cac75d2d4f96bb1f1a8056e6c96ef36cb538b6ce1d90150211000000024ac5aa02000000000000000000

1 output(s) for total of 0.476932043244 xmr

stealth address amount amount idx tag
00: a5dcd9c8b338f6587f37acca7dc48bdea095c8228f41499659d0d00651205c99 0.476932043244 55199 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": 33076, "vin": [ { "gen": { "height": 33066 } } ], "vout": [ { "amount": 476932043244, "target": { "key": "a5dcd9c8b338f6587f37acca7dc48bdea095c8228f41499659d0d00651205c99" } } ], "extra": [ 1, 135, 27, 154, 152, 144, 207, 14, 219, 149, 202, 199, 93, 45, 79, 150, 187, 31, 26, 128, 86, 230, 201, 110, 243, 108, 181, 56, 182, 206, 29, 144, 21, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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: