Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1424564b6954e6d1a8ee9e64800ebebf22f9a225e49f833addfdcb91fcf516f3

Tx prefix hash: c9a01ba356af5a4df5015d6ddf8a19d56d22926ce98046a2266b40f53a9969ba
Tx public key: f363d40e7b0d121434a9817c9f80b3ae3dfe7033f132110d837b4acc0c90e1f3
Timestamp: 1763564416 Timestamp [UCT]: 2025-11-19 15:00:16 Age [y:d:h:m:s]: 00:052:05:23:12
Block: 1415596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37409 RingCT/type: yes/0
Extra: 01f363d40e7b0d121434a9817c9f80b3ae3dfe7033f132110d837b4acc0c90e1f302110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ef5040632eb0e70212aa769b6bd46a0dc44a31f4ab9fc5cb1146c3652077cd1 0.600000000000 1904099 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": 1415606, "vin": [ { "gen": { "height": 1415596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ef5040632eb0e70212aa769b6bd46a0dc44a31f4ab9fc5cb1146c3652077cd1" } } ], "extra": [ 1, 243, 99, 212, 14, 123, 13, 18, 20, 52, 169, 129, 124, 159, 128, 179, 174, 61, 254, 112, 51, 241, 50, 17, 13, 131, 123, 74, 204, 12, 144, 225, 243, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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