Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 563ce2d0aa55c1ad6e3297a4cd998e536cbb9ba152b53ba53433fec64e767f3e

Tx prefix hash: 137b2983a1fa2ad496ea846885461c973716f13219b0cb7915cd0ff2497ca3b8
Tx public key: aa24134b3d03b5a28baa90a10ca84d4d5b291fb573db996945152ac0ae2a02bb
Timestamp: 1719859204 Timestamp [UCT]: 2024-07-01 18:40:04 Age [y:d:h:m:s]: 01:175:05:04:18
Block: 1056381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383816 RingCT/type: yes/0
Extra: 01aa24134b3d03b5a28baa90a10ca84d4d5b291fb573db996945152ac0ae2a02bb0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c69e15561a5493cb87f28f2a9caa2b6c0180c0e5db1247cf79f87c72a36ba2d4 0.600000000000 1526794 of 15

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 dinasty-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": 1056391, "vin": [ { "gen": { "height": 1056381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c69e15561a5493cb87f28f2a9caa2b6c0180c0e5db1247cf79f87c72a36ba2d4" } } ], "extra": [ 1, 170, 36, 19, 75, 61, 3, 181, 162, 139, 170, 144, 161, 12, 168, 77, 77, 91, 41, 31, 181, 115, 219, 153, 105, 69, 21, 42, 192, 174, 42, 2, 187, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8