Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b92e95061c8d183eb056730d3774a8a88bc96f9ca6cce3de9c90ceef9e6aceb2

Tx prefix hash: cb8441d48757c01fb79a45eca5643bfa023898c303d62d631041a3fbd53b6613
Tx public key: 4be192e3c675f9b985ef8d02292924438ac6501259f01e410e79204b08b71289
Timestamp: 1577160531 Timestamp [UTC]: 2019-12-24 04:08:51 Age [y:d:h:m:s]: 06:059:15:59:17
Block: 30337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1451090 RingCT/type: yes/0
Extra: 014be192e3c675f9b985ef8d02292924438ac6501259f01e410e79204b08b712890211000000028a2ee0d9000000000000000000

1 output(s) for total of 0.486960873986 xmr

stealth address amount amount idx tag
00: 374bf2a747958baf71f674cde3a828e9f60525e655b2d17c0cb034751393e08a 0.486960873986 50093 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": 30347, "vin": [ { "gen": { "height": 30337 } } ], "vout": [ { "amount": 486960873986, "target": { "key": "374bf2a747958baf71f674cde3a828e9f60525e655b2d17c0cb034751393e08a" } } ], "extra": [ 1, 75, 225, 146, 227, 198, 117, 249, 185, 133, 239, 141, 2, 41, 41, 36, 67, 138, 198, 80, 18, 89, 240, 30, 65, 14, 121, 32, 75, 8, 183, 18, 137, 2, 17, 0, 0, 0, 2, 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) | dinastycoin version: tesla-369