Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28eb93ec380b528f357cd0268d6128e33d8bebfa4bdca742756cdfe5c6056515

Tx prefix hash: 8a7cdcb0e69674001caf03e3aa6c5450269abad6e212713498c62c70bb961d43
Tx public key: c1b08fb0b12f128e3e23e90bac18b92ee71c3297246495f9945568e0fa945c11
Timestamp: 1585734158 Timestamp [UTC]: 2020-04-01 09:42:38 Age [y:d:h:m:s]: 06:229:10:40:16
Block: 90629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1588511 RingCT/type: yes/0
Extra: 01c1b08fb0b12f128e3e23e90bac18b92ee71c3297246495f9945568e0fa945c11021100000003209b4bc8000000000000000000

1 output(s) for total of 0.307403830945 xmr

stealth address amount amount idx tag
00: b1bb86760a6b55e9b7be116b1fa883f67b53cec337123492fae07a042699024a 0.307403830945 162293 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": 90639, "vin": [ { "gen": { "height": 90629 } } ], "vout": [ { "amount": 307403830945, "target": { "key": "b1bb86760a6b55e9b7be116b1fa883f67b53cec337123492fae07a042699024a" } } ], "extra": [ 1, 193, 176, 143, 176, 177, 47, 18, 142, 62, 35, 233, 11, 172, 24, 185, 46, 231, 28, 50, 151, 36, 100, 149, 249, 148, 85, 104, 224, 250, 148, 92, 17, 2, 17, 0, 0, 0, 3, 32, 155, 75, 200, 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: