Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 489f080fe56054b1809a4885cb60f600d4760a38dfbb6044dd66193427b24975

Tx prefix hash: 79afd3e082d35d0d9715923ab78e90e64f163ca549b6b80c58b4be8609630d75
Tx public key: 8493b1c5bd8020d9b0e69443cbcbf06bed42e084bf56d8f87c2fa2697c415182
Timestamp: 1714178345 Timestamp [UCT]: 2024-04-27 00:39:05 Age [y:d:h:m:s]: 01:033:04:54:04
Block: 1009285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284694 RingCT/type: yes/0
Extra: 018493b1c5bd8020d9b0e69443cbcbf06bed42e084bf56d8f87c2fa2697c41518202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5389a7df23f5a0147f9035b9de8705e31e68b7c01928d1e35ec82d08e4a5bb4a 0.600000000000 1470913 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": 1009295, "vin": [ { "gen": { "height": 1009285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5389a7df23f5a0147f9035b9de8705e31e68b7c01928d1e35ec82d08e4a5bb4a" } } ], "extra": [ 1, 132, 147, 177, 197, 189, 128, 32, 217, 176, 230, 148, 67, 203, 203, 240, 107, 237, 66, 224, 132, 191, 86, 216, 248, 124, 47, 162, 105, 124, 65, 81, 130, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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