Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f865d51bdbd7834b09324b1bdc3d1f846fd53498a1e59b1dafb039d85d0035

Tx prefix hash: 3788bf74010c9cefa5848f733f6084a4e23a087f58339830947e70fe02980fc1
Tx public key: add5d755b26f0b737d79f279a99ad2243f9f145f25c2b1b1f8f1832b60e62c28
Timestamp: 1577544633 Timestamp [UTC]: 2019-12-28 14:50:33 Age [y:d:h:m:s]: 06:244:18:18:59
Block: 33560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1589220 RingCT/type: yes/0
Extra: 01add5d755b26f0b737d79f279a99ad2243f9f145f25c2b1b1f8f1832b60e62c280211000000038a2ee0d9000000000000000000

1 output(s) for total of 0.475119270717 xmr

stealth address amount amount idx tag
00: 0702d1c099b66dc5448867ea837f08be6be0a874131ff966203dd44f5d5ace38 0.475119270717 56237 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": 33570, "vin": [ { "gen": { "height": 33560 } } ], "vout": [ { "amount": 475119270717, "target": { "key": "0702d1c099b66dc5448867ea837f08be6be0a874131ff966203dd44f5d5ace38" } } ], "extra": [ 1, 173, 213, 215, 85, 178, 111, 11, 115, 125, 121, 242, 121, 169, 154, 210, 36, 63, 159, 20, 95, 37, 194, 177, 177, 248, 241, 131, 43, 96, 230, 44, 40, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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: