Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d068725b31e65b4061f576500926091651328036e5b12d39e851825674d779e

Tx prefix hash: bd92973f7c6325ed9b5e26d72b79c6d9928d1c1abf68c82ebd274c2f0b8a8532
Tx public key: 8b3236a1cc5e0472a939ec7402962ef0500e86f80e4cc4be23ef6cd4fa161610
Timestamp: 1578363975 Timestamp [UTC]: 2020-01-07 02:26:15 Age [y:d:h:m:s]: 06:029:12:09:36
Block: 40224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1429605 RingCT/type: yes/0
Extra: 018b3236a1cc5e0472a939ec7402962ef0500e86f80e4cc4be23ef6cd4fa161610021100000017391a8d0e000000000000000000

1 output(s) for total of 0.451566834531 xmr

stealth address amount amount idx tag
00: cf0c0672da31fbb255524cb3c7b2ff4fe838f16cb16ab8fad81e4509605c3b87 0.451566834531 70362 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": 40234, "vin": [ { "gen": { "height": 40224 } } ], "vout": [ { "amount": 451566834531, "target": { "key": "cf0c0672da31fbb255524cb3c7b2ff4fe838f16cb16ab8fad81e4509605c3b87" } } ], "extra": [ 1, 139, 50, 54, 161, 204, 94, 4, 114, 169, 57, 236, 116, 2, 150, 46, 240, 80, 14, 134, 248, 14, 76, 196, 190, 35, 239, 108, 212, 250, 22, 22, 16, 2, 17, 0, 0, 0, 23, 57, 26, 141, 14, 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) | dinastycoin version: tesla-369