Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbeca42dfb3a532b3e4cb6e654b59b31386946a483d8ab746724439216a6f457

Tx prefix hash: 2feb7ce116234af8a4b887d22e09ee08d5dc579a3d814c5353b6732c4e99ee45
Tx public key: a6c3da4a628ff6efaab13aa03d636b46132ef522e445ff49c6ee403708243c8b
Timestamp: 1577204629 Timestamp [UTC]: 2019-12-24 16:23:49 Age [y:d:h:m:s]: 06:271:20:39:23
Block: 30878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1608779 RingCT/type: yes/0
Extra: 01a6c3da4a628ff6efaab13aa03d636b46132ef522e445ff49c6ee403708243c8b021100000133c5b5978f000000000000000000

1 output(s) for total of 0.484941363172 xmr

stealth address amount amount idx tag
00: 239aa23f7d197c42f1d14507cbc4fa2ecb678a9d26f29b6663a5af18da10b61e 0.484941363172 50958 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": 30888, "vin": [ { "gen": { "height": 30878 } } ], "vout": [ { "amount": 484941363172, "target": { "key": "239aa23f7d197c42f1d14507cbc4fa2ecb678a9d26f29b6663a5af18da10b61e" } } ], "extra": [ 1, 166, 195, 218, 74, 98, 143, 246, 239, 170, 177, 58, 160, 61, 99, 107, 70, 19, 46, 245, 34, 228, 69, 255, 73, 198, 238, 64, 55, 8, 36, 60, 139, 2, 17, 0, 0, 1, 51, 197, 181, 151, 143, 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: