Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 143ad83b04af0b78ef159b6cc4c6c23f7c46133098e65029870397d9734bded4

Tx prefix hash: b6e2858e0a2425f269a3065123c7f92502029f7b2e68437bda9d41e0ef04dbe4
Tx public key: 0d9c3975875033993bcc4c26c03b259d29641c59ae66520cabeb0a250167d01b
Timestamp: 1714304015 Timestamp [UCT]: 2024-04-28 11:33:35 Age [y:d:h:m:s]: 00:210:06:00:20
Block: 1010327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150507 RingCT/type: yes/0
Extra: 010d9c3975875033993bcc4c26c03b259d29641c59ae66520cabeb0a250167d01b0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bc84e5aa427f0fb5e63618880d2da3f49d6ad16d17b17410a4fe6a9f87a56d9 0.600000000000 1472249 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": 1010337, "vin": [ { "gen": { "height": 1010327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bc84e5aa427f0fb5e63618880d2da3f49d6ad16d17b17410a4fe6a9f87a56d9" } } ], "extra": [ 1, 13, 156, 57, 117, 135, 80, 51, 153, 59, 204, 76, 38, 192, 59, 37, 157, 41, 100, 28, 89, 174, 102, 82, 12, 171, 235, 10, 37, 1, 103, 208, 27, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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